Keith Medcalf, (quoting Llyod), writes: >> >How can I build the dll correctly?
> cl -DSQLITE_API=__declspec(dllexport) sqlite3.c -link -dll -out:sqlite3.dll I do not claim here that “correctly” building the DLL must be done as either I or Keith has suggested. However, the method using Makefile.msc accomplishes a few things that the do-it-all-almost CL invocation does not. For example, it compiles sqlite3.rc as a resource source and causes information such as the file version, source id, copyright, etc. to be linked into the DLL as a resource. (This can be seen in Windows file explorer by right-clicking on the DLL, clicking the “Properties” button, then clicking the “Details” tab.) With either method, it is possible to set a great many compile options. The makefile has provisions for setting them in a consistent way. And as ‘make’ aficionados know, it is a very convenient place to keep track of and reuse how you want to build something. That said, standalone CL invocation is great for just getting something made quickly when bothering with more files is just excess bother. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
