jeans/motioneyeos
jeans/motioneyeos
1
0
Fork 0
mirror of https://github.com/motioneye-project/motioneyeos.git synced 2025-07-29 22:26:31 +00:00
Code Issues Packages Projects Releases Wiki Activity

sqlite: Add new compile-time options

Browse Source 
[Peter: whitespace/wording tweaks]
Signed-off-by: Stefan Froberg <stefan.froberg@petroprogram.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
This commit is contained in:
Stefan Fröberg 2012-08-12 09:17:00 +00:00 committed by Peter Korsgaard
parent 7655b95e27
commit ef1e76ae43
2 changed files with 46 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
package/sqlite/Config.in
View File

@ -22,3 +22,37 @@ config BR2_PACKAGE_SQLITE_STAT3
planner that can help SQLite to choose a better query plan under planner that can help SQLite to choose a better query plan under
certain situations. certain situations.
config BR2_PACKAGE_SQLITE_ENABLE_FTS3
bool "Enable version 3 of the full-text search engine"
depends on BR2_PACKAGE_SQLITE
help
When this option is defined in the amalgamation
(see http://www.sqlite.org/amalgamation.html), version 3 of
the full-text search engine is added to the build automatically.
config BR2_PACKAGE_SQLITE_ENABLE_UNLOCK_NOTIFY
bool "Enable sqlite3_unlock_notify() interface"
depends on BR2_PACKAGE_SQLITE
help
This option enables the sqlite3_unlock_notify() interface and its
accosiated functionality. See the documentation
http://www.sqlite.org/unlock_notify.html for additional information.
config BR2_PACKAGE_SQLITE_SECURE_DELETE
bool "Set the secure_delete pragma on by default"
depends on BR2_PACKAGE_SQLITE
help
This compile-time option changes the default settings of the
secure_delete pragma. When this option is not used, secure_delete
defaults to off. When this option is present, secure_delete defaults
to on.
The secure_delete setting causes deleted content to be overwritten
with zeros. There is a small performance penalty for this since
additional I/O must occur. On the other hand, secure_delete can
prevent sensitive information from lingering in unused parts
of the database file after it has allegedly been deleted.
See the documentation on the
http://www.sqlite.org/pragma.html#pragma_secure_delete
for additional information.

12
package/sqlite/sqlite.mk
View File

@ -21,6 +21,18 @@ ifeq ($(BR2_PACKAGE_SQLITE_STAT3),y)
SQLITE_CFLAGS += -DSQLITE_ENABLE_STAT3 SQLITE_CFLAGS += -DSQLITE_ENABLE_STAT3
endif endif
ifeq ($(BR2_PACKAGE_SQLITE_ENABLE_FTS3),y)
SQLITE_CFLAGS += -DSQLITE_ENABLE_FTS3
endif
ifeq ($(BR2_PACKAGE_SQLITE_ENABLE_UNLOCK_NOTIFY),y)
SQLITE_CFLAGS += -DSQLITE_ENABLE_UNLOCK_NOTIFY
endif
ifeq ($(BR2_PACKAGE_SQLITE_SECURE_DELETE),y)
SQLITE_CFLAGS += -DSQLITE_SECURE_DELETE
endif
SQLITE_CONF_ENV = CFLAGS="$(TARGET_CFLAGS) $(SQLITE_CFLAGS)" SQLITE_CONF_ENV = CFLAGS="$(TARGET_CFLAGS) $(SQLITE_CFLAGS)"
SQLITE_CONF_OPT = \ SQLITE_CONF_OPT = \