Am 15.05.2011 20:43, schrieb Amy and Steve: > Thanks! I will study the sqlite3_auto_extension closer. I had trouble > compiling the ext....c file, but I can't remember what the errors were > and I just got back in town, so I will have to work my back to trying to > compile it.
I remember I had also some problems in compiling the extension functions' module, but after applying some minor changes I managed to compile it together with my implementation of an encryption extension. You find the modified version of extensionfunctions.c here: http://wxcode.svn.sourceforge.net/viewvc/wxcode/trunk/wxCode/components/wxsqlite3/sqlite3/secure/src/codec-c/ > On 05/10/2011 01:24 PM, Mays, Steve wrote: >>> Question 1.) Can "exentension_functions.c" be compiled along with >>> "sqlite3.c" into one executable? >>> >>> Question 2.) If so, how? >>> >>> Question 3.) If "exentension_functions.c" be compiled into one >>> executable along with "sqlite3.c", do I need to do anything special or >>> will sqlite3_exec() know what to do with queries like: >> You can compile together into one binary but the SQLite main code won't know >> that your code co-exists. There are two options available to you: >> >> 1 - [Not recommended] Patch the internal openDatabase method to call your >> init method (this is how the extensions distributed with SQLite are added). >> >> 2 - Call sqlite3_auto_extension from your code that does SQLite >> initialization. There is a 3rd option using the C preprocessor to your advantage without the need to change the original SQLite amalgamation sources. Take a look at file sqlite3secure.c in the above mentioned SVN repository. Regards, Ulrich _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
