Christian, I understand Windows is poor, but I do not fully understand the compilation process. The mkopc3.exe is actually created- so this itself cannot be the problem. Not having awk doesn't seem to be an issue for compiling the 3.2.1-based driver either (see 1).
Sorry, I'm confused :( Andi -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christian Werner Sent: Dienstag, 16. Mai 2006 09:04 To: sqlite-users@sqlite.org Subject: Re: [sqlite] Compiling Sqlite JDBC driver (Compiler question) [EMAIL PROTECTED] wrote: > > After I've been able to overcome the initial compiler problem (missing > library installation), I'm faced with a new one: > > 1) Compiling JDBC wrapper for 3.2.1 works fine > > 2) Compiling JDBC wrapper for 3.3.5 fails: > > cl -Gs -EHsc -D_WIN32 -nologo -Zi -DOS_WIN=1 > -D_CRT_SECURE_NO_DEPRECATE > -DNDEBUG=1 -DSQLITE_OMIT_CURSOR=1 -DWIN32=1 -DTHREADSAFE=1 -DOS_WIN=1 > -DSQLITE_S > OUNDEX=1 -I. -I..\sqlite-3.3.5/src -D_DLL -c > ...\sqlite-3.3.5/src/alter.c alter.c > ...\sqlite-3.3.5/src/alter.c(70) : error C2065: 'TK_SPACE' : > undeclared identifier > > Regarding TK_SPACE, I've found that parse.y has changed between the > two version, where 3.3.5 version now omits these lines: > > %nonassoc END_OF_FILE ILLEGAL SPACE UNCLOSED_STRING COMMENT FUNCTION > COLUMN AGG_FUNCTION. > > I've not been able to figure out where or how TK_SPACE should be > generated for the parse.h Please use the mkopc3.c source from the sqlite odbc driver instead. It should deal with this issue (poor MSWindows development systems weren't born with an awk :( another reason to switch to cygwin or mingw). Anybody volunteering for creating the build environment of javasqlite with the cygwin or mingw toolchain ? Regards, Christian This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
