On 6/11/18, Lonnie Abelbeck <li...@lonnie.abelbeck.com> wrote: > >> On Jun 11, 2018, at 7:23 AM, Richard Hipp <d...@sqlite.org> wrote: >> >> On 6/11/18, Lonnie Abelbeck <li...@lonnie.abelbeck.com> wrote: >>> >>> What changed for 3.23.1 -> 3.24.0 to cause such a large increase in >>> library >>> file size? >>> >> >> See Dan's follow-up. Beginning with 3.24.0, the FTS5 and JSON1 >> extensions are enabled by default. >> >> Manually edit the Makefile generated by ./configure to turn off those >> two features. You ought to be able to do "./configure --disable-fts5 >> --disable-json1" but those two --disable options appear to be broken >> in the ./configure script. > > Quick note, I added --disable-fts5 --disable-json1 to configure ... > > Then 3.24.0 when from 814112 bytes to 683648 bytes, also removed -lm > dependancy. > > Ref: For the amalgamation-tarball, enable FTS5 and JSON1 by default > https://www.sqlite.org/src/vinfo/03edecaf9dcfc927?diff=1 > > Is there a reason we should not disable FTS5 and JSON1 going forward for > embedded use ?
There are two configure scripts (1) The main configure script at the root of the source tree, used to build from canonical sources. (2) The configure script at autoconf/configure.ac that generates the configure script that is part of the prepackaged amalgamation deliverables. Dan was talking about (2) and he is correct that FTS5 and JSON1 went from default-off to default-on in version 3.24.0. I was talking about (1) which did not change its default settings, but which does have the bug in which the --disable-fts5 and --disable-json1 flags seem to be ignored. There is no reason to include FTS5 and JSON1 in embedded builds if you do not need them. -- 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
