From d6d64068d972efca02a832e4e01ade65ad9b443c Mon Sep 17 00:00:00 2001 From: Stephen Lombardo Date: Tue, 12 Oct 2010 15:31:27 -0700 Subject: [PATCH] clarify build with temp store options --- README | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README b/README index 89c88223..d964a725 100644 --- a/README +++ b/README @@ -23,17 +23,17 @@ If you are using SQLCipher in your own software please let us know at support@ze Building SQLite Cipher is almost the same as compiling a regular version of SQLite with three small exceptions: 1. building via 'amalgamation' isn't supported (where all sqlite source is merged into one file) - 2. you must define SQLITE_HAS_CODEC + 2. you must define SQLITE_HAS_CODEC and SQLITE_TEMP_STORE=2 in your application when including SQLCipher 3. You need to link against a OpenSSL's libcrypto with sha256 support compiled in Example Static linking (replace /opt/local/lib with the path to libcrypto.a) - ./configure CFLAGS="-DSQLITE_HAS_CODEC" LDFLAGS="/opt/local/lib/libcrypto.a" + ./configure --enable-tempstore=yes CFLAGS="-DSQLITE_HAS_CODEC" LDFLAGS="/opt/local/lib/libcrypto.a" make Example Dynamic linking - ./configure CFLAGS="-DSQLITE_HAS_CODEC" LDFLAGS="-lcrypto" + ./configure --enable-tempstore=yes CFLAGS="-DSQLITE_HAS_CODEC" LDFLAGS="-lcrypto" make [Encrypting a database]