That's what I do. Once your makefile is set up, make the "sqlite3.c" target if you want an amalgamated source file. Be sure to carefully coordinate the defined values between the preprocessing step (to generate your source file(s)) and the build of your application/dll.
If you are using amalgamated source, you may find a few other small problems when building your app, but they are easy to fix. Richard Klein wrote: >> Richard Klein wrote: >> >>> In order to reduce SQLite's memory footprint in my embedded >>> application, I want to use the SQLITE_OMIT_xxx options to >>> remove unneeded features from SQLite. >>> >>> Using Cygwin running on Windows, I have successfully down- >>> loaded the canonical sources and autoconfigured the Makefile. >>> >>> The Makefile seems to indicate that in order to generate >>> the parser, opcodes, and keyword hash function so that they >>> omit the unneeded features, I need only add the following >>> line to the Makefile: >>> >>> OPTS = -DSQLITE_OMIT_xxx -DSQLITE_OMIT_yyy ... >>> >>> Is this correct? >>> >>> >> I believe so, but I haven't ever used the OMIT options when building SQLite. >> >> Are you having a problem when you do this? >> >> Dennis Cote >> >> > I haven't tried it yet ... I'll let you know if I have any > problems. Thanks! > > - Richard > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
