[EMAIL PROTECTED] wrote: > > 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, from SQLite 3.2.1 to 3.3.5 some automagic in creating opcodes.h and parse.h has changed significantly. The mkopc3.exe does on Windows what main.mk in the SQLite source does by using the awk scripts mkopcode{c,h}.awk and addopcodes.awk. The mkopc3 source in the latest javasqlite is not up to date and not ready for 3.3.5 (but mkopc3 in the latest ODBC driver is). You have two options: setup your make of the Java wrapper to use sqlite.dll or (as in my original tarballs) build SQLite as a link library and link it directly into sqlite_jni.dll. The former is maybe easier to achieve, the latter does not require to have sqlite.dll installed in the right place. Hope that helps, Christian