-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Brown, Daniel wrote: > I am not using the amalgamation version of the source as I have our my > VFS implementations for two of the platforms I work with based on the > original win_os.c VFS and the amalgamation does not provide the > necessary header files (os_common.h and sqliteInt.h) to make VFS > integration possible. Other than by inserting the source for my VFS > implementations directly into the amalgamation source, which I'd rather > not do as it would make upgrading to new SQLite versions much more > complex.
You can do what I do which is the other way round. I #include the sqlite3.c amalgamation into my one file that does database access, implements vtables and vfs etc. You can make all the SQLite symbols private even: /* See SQLite ticket 2554 */ #define SQLITE_API static #define SQLITE_EXTERN static Using the amalgamation vs individual source files gives a reported 5-10% performance improvement. I haven't measured what you then get when #including the amalgamation above your database code, but did notice when using the debugger that the compiler inlined quite a few methods. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkk05GEACgkQmOOfHg372QSPXgCfcyym8qyxmz452C01OKnUOJaJ eycAoKyFi6kjHkua96crnZl2NcKZlCHl =Ox7s -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
