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

2018-04-06 Thread petern
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: https://www.sqli

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

2018-04-06 Thread Max Vlasov
Oh, I see, just looked at the examples, all you described works thanks to the magic of c preprocessor. The problem in my case is that I'm on Delphi. Plus I already has something like indirect access to sqlite api functions, I will probably make a converter during the init between sqlite3Apis and my

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

2018-04-05 Thread Keith Medcalf
You write the code as if it were a loadable extension. If you compile "inline" (ie, appended to the amalgamation) the headers will detect the SQLITE_CORE symbol being defined and generate direct calls rather than indirect calls. There is really no need to change the code from the code you w