Yes I tried using the amalgamation, but I still don't get as good result as I did before with 3.3.13...
Also, when I defined SQLITE_OMIT_ALTERTABLE I got this error: error LNK2019: unresolved external symbol _sqlite3AlterBeginAddColumn referenced in function _yy_reduce error LNK2019: unresolved external symbol _sqlite3AlterFinishAddColumn referenced in function _yy_reduce error LNK2019: unresolved external symbol _sqlite3AlterRenameTable referenced in function _yy_reduce Best regards, Jonas On 6/13/07, Andrew Finkenstadt <[EMAIL PROTECTED]> wrote:
On 6/13/07, Jonas Sandman <[EMAIL PROTECTED]> wrote: > > Hello, > > Is it possible to get the latest SQLite somehow which doesn't require you > to > actually run "make"? > > With the amalgamation (?) you can just compile the whole thing in Visual > Studio but it seems that the compiler isn't very successful in optimizing > when it's run like that since my application swelled another 39 kb just > because I used an amalgamation-compiled library instead of 3.3.13 which I > compiled earlier (not sure where I got all the working header-files for > that > one, maybe they were present back then?) > > Best regards, > Jonas > I use SQlite to some success in Visual Studio 2005. I use the amalgamation exclusively, and I compile in "C++" mode. I also predefine SQLITE_option strings that disable features that are not necessary in my application, which reduces code size. The result of this step is an object file sqlite3.obj which I then link into the remainder of my application framework that uses sqlite3 facilities. Nowhere a make appears in that process.
