From: Stefan Froberg <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] sqlite: Add new compile-time options
Date: Sun, 12 Aug 2012 22:17:00 +0300 [thread overview]
Message-ID: <1344799020-27916-2-git-send-email-stefan.froberg@petroprogram.com> (raw)
In-Reply-To: <1344799020-27916-1-git-send-email-stefan.froberg@petroprogram.com>
Signed-off-by: Stefan Froberg <stefan.froberg@petroprogram.com>
---
package/sqlite/Config.in | 34 ++++++++++++++++++++++++++++++++++
package/sqlite/sqlite.mk | 12 ++++++++++++
2 files changed, 46 insertions(+), 0 deletions(-)
diff --git a/package/sqlite/Config.in b/package/sqlite/Config.in
index 25aaa3f..75bce70 100644
--- a/package/sqlite/Config.in
+++ b/package/sqlite/Config.in
@@ -22,3 +22,37 @@ config BR2_PACKAGE_SQLITE_STAT3
planner that can help SQLite to choose a better query plan under
certain situations.
+config BR2_PACKAGE_SQLITE_ENABLE_FTS3
+ bool "Enables 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 "Enables 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 "Sets 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.
+
diff --git a/package/sqlite/sqlite.mk b/package/sqlite/sqlite.mk
index 9e63b52..745bf2a 100644
--- a/package/sqlite/sqlite.mk
+++ b/package/sqlite/sqlite.mk
@@ -20,6 +20,18 @@ ifeq ($(BR2_PACKAGE_SQLITE_STAT3),y)
SQLITE_CFLAGS += -DSQLITE_ENABLE_STAT3
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_OPT = \
--
1.7.7.6
next prev parent reply other threads:[~2012-08-12 19:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-12 19:16 [Buildroot] [PATCH] sqlite: Add new compile-time options Stefan Froberg
2012-08-12 19:17 ` Stefan Froberg [this message]
2012-11-04 11:16 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1344799020-27916-2-git-send-email-stefan.froberg@petroprogram.com \
--to=stefan.froberg@petroprogram.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox