On Monday, 4 December, 2017 15:03, Jens Alfke <j...@mooseyard.com> wrote: >> On Dec 4, 2017, at 11:59 AM, Keith Medcalf <kmedc...@dessus.com> >>wrote:
>> You should only be defining SQLITE_CORE if in fact the extension is >>part of the core -- that is compiled and included (statically linked) >>to the core sqlite3.c compilation unit. >Which it is, in this case. The OP said that both sqlite and the >extension are static libraries, so they’re both being linked directly >into the executable. Hmmm. You are right. I read is as statically linked loadlibs (DLLs) not as all the object modules were linked together into a single executable; then you are right, there should not be an issue. However, each compilation unit still must be using the same single uniform runtime library. If one object is using, for example, the multithreaded runtime and the others are using the single threaded runtime (for example), and the third perhaps the subsystem runtime, you will end up with the same runtime collisions after they are linked together. >I’m not sure what’s going on. Life, can you post a backtrace of the >crash? And perhaps use the dependency walker (depends.exe) on the executable and see if multiple runtimes are being loaded ... _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
