Re: [sqlite] Access to sqlite3_api_routines outside of a loadable extension context

Max. You are free to export your code differently by preprocessor directives. One binary of your code can be an extension and another can be an ordinary library. The loadable version binary simply needs to export a working sqlite3_extension_init() C entrypoint as described here:

Re: [sqlite] Access to sqlite3_api_routines outside of a loadable extension context

te-users [mailto:sqlite-users- > >boun...@mailinglists.sqlite.org] On Behalf Of Max Vlasov > >Sent: Thursday, 5 April, 2018 09:24 > >To: SQLite mailing list > >Subject: [sqlite] Access to sqlite3_api_routines outside of a > >loadable extension context > > > &g

Re: [sqlite] Access to sqlite3_api_routines outside of a loadable extension context

sqlite] Access to sqlite3_api_routines outside of a >loadable extension context > >Hi, >I'm considering creating a virtual table or user function that might >possible work either as a loadable extension or as a general, >statically >created one. In order to avoid repeating during de

[sqlite] Access to sqlite3_api_routines outside of a loadable extension context

Hi, I'm considering creating a virtual table or user function that might possible work either as a loadable extension or as a general, statically created one. In order to avoid repeating during developing, I thought that I might use sqlite3_api_routines structure as a universal access to sqlite