The answer of "just add sqlite.c to your project" is great when you're making something in C. The entire world does not use C, nor is C (or C++) always the best option for a particular project.
Timothy Uy's offer actually makes a lot of sense if you're using something other then C or C++. For example, I just can't ship a .Net .exe that uses x-copy deployment, and runs on Linux/Mac (via Mono) unless I invest about 40-80 hours digging deep into how System.Data.SQLite.dll is built. On Tue, Jun 26, 2012 at 9:10 AM, Simon Slavin <slav...@bigfraud.org> wrote: > > On 26 Jun 2012, at 4:55pm, bi...@aol.com wrote: > >> Thank you everyone who took the time to comment on my Windows DLL question. >> I'm also glad I'm not the only one who sees the problem with not having >> the version in the resource block. This really would have helped when Chrome >> and Firefox updated to a new version of SQLite and all my code stopped >> working. > > This is the reason you will see so many posts here telling you to build > SQLite into your application instead of using a DLL. Then you are not > subject to the choices of any other person with code on your users' > computers. SQLite purposely issued a compact and simple amalgamation version > of the source code especially to make this fast and simple. > > Simon. > _______________________________________________ > 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
