The warnings are normal and unless you want to rewrite sqlite, not much you can do about them.
Not sure about the run-time check failure _____ From: Dixon Hutchinson [mailto:[EMAIL PROTECTED] Sent: Wednesday, 20 September 2006 8:41 AM To: sqlite-users@sqlite.org Subject: [sqlite] Difficulty with sqlite3.3.6 under VisualStudio.net I am having difficulty getting a clean build under Visual Studio. I believe I have followed the advice given at http://www.sqlite.org/cvstrac/wiki?p=VsNetSolution. I am getting lots of errors of the sort: ...\\sqlite3\\vdbemem.c(194) : warning C4267: '=' : conversion from 'size_t' to 'int', possible loss of data ...\\sqlite3\\vdbemem.c(319) : warning C4244: '=' : conversion from 'double' to 'i64', possible loss of data ...\\sqlite3\\vdbemem.c(779) : warning C4311: 'type cast' : pointer truncation from 'char *' to 'int' ...\\sqlite3\\vdbeaux.c(531) : warning C4267: 'initializing' : conversion from 'size_t' to 'int', possible loss of data ...\\sqlite3\\vdbeaux.c(564) : warning C4018: '<=' : signed/unsigned mismatch ...\\sqlite3\\vdbeaux.c(659) : warning C4267: '=' : conversion from 'size_t' to 'int', possible loss of data I could just turn off the warnings, but that seems kind of wreckless. The output from the compile is attached. I am also getting: Run-Time Check Failure #2 - Stack around the variable 'ts' was corrupted." This is in vdbe.c Although it is not at the same variable every time. I am running a single threaded app. This is what has lead me to want to fix the compiler warnings. Any suggestions? I'm hoping for a recommended change in my preprocessors settings. Drastic modifications to sqlite does not seem appropriate. Current preprocessor definitions are: WIN32 WINVER=0x0500 _WIN32_WINNT=0x0500 _DEBUG _WINDOWS _USRDLL NO_TCL SQLITE3_EXPORTS _WINDLL _UNICODE UNICODE
