Do like a lot of us do and forget the DLL and just put sqlite3.c/h into your project.
Then you can build and forget about it and it will always work in your project (barring any future 32/64 incompatibilities). And you don't have to worry about who's testing what bitset as it's completely self-contained. Michael D. Black Senior Scientist Advanced Analytics Directorate Advanced GEOINT Solutions Operating Unit Northrop Grumman Information Systems ________________________________ From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on behalf of Peter Zoll [pz...@imagsts.com] Sent: Wednesday, December 07, 2011 2:54 PM To: sqlite-users@sqlite.org Subject: EXT :[sqlite] Building Windows applications On a Windows 7 64 bit desktop machine we downloaded the 64-bit SQlite dll. As can be seen at http://www.imagsts.com/BeisaTechnical.html we had to change a parameter in Visual Studio 2010 for the application to run inside Visual Studio (typical debugging mode). All seemed well until we went to build the MSI. Our current thinking is we need to point the SetupProject to the 32-bit dll so that beta testers can do something, albeit on 32-bit machines. If that works, we are still unclear how a 64-bit app could be generated. We are aware that it is unlikely our app would need to be 64-bit, but it does raise some questions about developing with one dll and distributing another. It seems like someone must have already solved this problem (with an answer besides 'buy a Mac') _______________________________________________ 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
