This should be simple: just add your own version of the Amalgamation C file (sqlite3.c) instead of linking to libsqlite3.dylib. There may be some issues for investigation, such as correct default path, using a prefix to avoid function name collision, etc. but otherwise this issue should be about testing and documentation.
The real benefit would be a smooth transition to enhancements such as SQLCipher, see http://sqlcipher.net/ios-tutorial/
Finally, it would really be great to have a unified interface with the Javascript for iOS and Android (see #6)
This should be simple: just add your own version of the Amalgamation C file (sqlite3.c) instead of linking to libsqlite3.dylib. There may be some issues for investigation, such as correct default path, using a prefix to avoid function name collision, etc. but otherwise this issue should be about testing and documentation.
The real benefit would be a smooth transition to enhancements such as SQLCipher, see http://sqlcipher.net/ios-tutorial/
Finally, it would really be great to have a unified interface with the Javascript for iOS and Android (see #6)