configure --enable-load-extension --enable-threadsafe --with-readline-lib=auto --with-pic --enable-json1 --enable-fts3 --enable-fts4 --enable-fts5 --enable-rtree --enable-session --enable-update-limit --enable-geopoly
Adjust the configure parameters to include what you want included. --- The fact that there's a Highway to Hell but only a Stairway to Heaven says a lot about anticipated traffic volume. >-----Original Message----- >From: sqlite-users [mailto:sqlite-users- >boun...@mailinglists.sqlite.org] On Behalf Of Lindsay Lawrence >Sent: Friday, 2 November, 2018 18:12 >To: General Discussion of SQLite Database >Subject: Re: [sqlite] json_each() in a table trigger for an >'attached' db causes an error > >Hi, > >Sorry. I have had no luck with this. > >I followed the instructions here >https://www.sqlite.org/getthecode.html#clone >then built from source following the directions in README.md. > > mkdir bld ;# Build will occur in a sibling >directory > cd bld ;# Change to the build directory > ../sqlite/configure ;# Run the configure script > make ;# Run the makefile. > make sqlite3.c ;# Build the "amalgamation" source file > make test ;# Run some tests (requires Tcl) > >This is the platform I am building on 'uname -a': > >Linux debianE7440-LT 3.16.0-6-amd64 #1 SMP Debian 3.16.57-2 (2018-07- >14) >x86_64 GNU/Linux > >The current trunk source however does not have the JSON1 extension >embedded >in the amalgamation by default. How would I add that? >However, building the json1 extension against this source and then >loading >it from the shell reports this: > >SQLite version 3.8.10.1 2015-05-13 04:50:30 >Enter ".help" for usage hints. >Connected to a transient in-memory database. >Use ".open FILENAME" to reopen on a persistent database. >sqlite> .version >SQLite 3.8.10.1 2015-05-13 04:50:30 >59e3e9e764440b7feaafadff74f422535d21bca2 >sqlite> .load "../../../bin/json1" >Error: ../../../bin/json1.so: undefined symbol: >sqlite3_create_window_function >sqlite> > >I'll tinker with it a more but at this point I am not sure if it is >because an own build configuration issue trying to test your fix or >if the >fix itself is the issue. > >Regards, >/Lindsay > > >On Fri, Nov 2, 2018 at 10:38 AM Richard Hipp <d...@sqlite.org> wrote: > >> Please try your test script on the latest trunk check-in and let us >> know whether or not it is working for you. >> >> -- >> D. Richard Hipp >> d...@sqlite.org >> _______________________________________________ >> sqlite-users mailing list >> sqlite-users@mailinglists.sqlite.org >> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite- >users >> >_______________________________________________ >sqlite-users mailing list >sqlite-users@mailinglists.sqlite.org >http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users