Hello Papa, I just link it in as static library. Just include the code in each project or create a static lib project. It depends on the rest of your application though. If you're trying to static link the rest of the application then a static linked Sqlite makes sense. If you're dynamic linking the run time library, you might as well dynamic link Sqlite.
I find that generally, statically linked applications are more reliable in Windows. The problem isn't windows so much as the poor state of most of my user's PC's. C Wednesday, August 26, 2015, 1:03:18 PM, you wrote: pac> On my Win10, I'd like to compile SQLite3 to create a 64-bit pac> DLL. The intention is to use this DLL instead of the pac> amalgamation, this way more than one C++ application can access pac> the same DLL. Please note that I am an aficionado, not an expert pac> when it comes to C++ and for SQL, well, this would be my second pac> attempt to get an application to use a database, as opposed to flat files. pac> How would you suggest I should proceed? is this even a good idea? pac> _______________________________________________ pac> sqlite-users mailing list pac> sqlite-users at mailinglists.sqlite.org pac> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users -- Teg mailto:Teg at djii.com
