I have a situation where it would be convenient to locate externally loadable SQLite extension code in the same compilation unit as the server code. Is there a way for server main() to load those extensions located within its own compilation unit? Does the necessity of #including both sqlite3.h and sqlite3ext.h with SQLITE_EXTENSION_INIT1 macro rule this out?
Documentation suggests sqlite3_auto_extension() loads a statically linked extension entrypoint but trying this on same compilation unit's sqlite3_extension_init() entrypoint results in segfault. FYI, environment is Linux. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
