No comment at all? That's three users asking for this now. :( Patrick
-----Original Message----- From: Clark Christensen [mailto:[EMAIL PROTECTED] Sent: Friday, April 27, 2007 11:12 AM To: sqlite-users@sqlite.org Subject: Re: [sqlite] May I ask why the source distribution mechanism was changed starting with 3.3.14? In general, I agree. I miss the zipped set of pre-processed C source. Since you have the Linux-based build system at your disposal, you can get what you're used to having with make target_source on the Linux system. This creates a tsrc directory containing the familiar pre-processed C source for use in your Windows build. For what it's worth, I was able to build the sqlite3.dll on Windows (VC6) from the "amalgam" sqlite3.c file without having to have lemon or any of the other SQLite-specific build components - except that pesky sqlite3.def file. I still have to download the precompiled Win32 DLL to get that. Looking at the generated makefile (from the configure script) on Linux, I see there's a rule for making sqlite3.def. The algorithm (grep ... | sed ...) basically works on Windows, using the sqlite3.obj, but the resulting def is short a few lines compared to the one I downloaded. Last, I tried to build the shell from the compiled amalgam, but it errors-out on the link phase complaining about unresolved externals (sqlite3_iotrace or somesuch). And I don't have time right now to figure it out. I'm not a C programmer, and am unfamiliar with compilers, linkers, compiler options, and all that. I usually just have to do trial and error (lots of error) and eventually I figure it out. -Clark ----- Original Message ---- From: "Bennett, Patrick" <[EMAIL PROTECTED]> To: sqlite-users@sqlite.org Sent: Friday, April 27, 2007 6:57:38 AM Subject: [sqlite] May I ask why the source distribution mechanism was changed starting with 3.3.14? The last time I downloaded SQLite was version 3.3.12. For that version (and many prior versions), I could download a preprocessed archive containing all of the source code, except parse.h, parse.c and opcode.h(? - this is from memory) were the 'generated' versions. The source for the command-line shell was there as well as all other source code. This was close to ideal for me, as I was able to use it in our (custom) build system and build for Windows and Linux with almost no effort at all. Now, I have two choices: 1) Download a tar of everything and have a version of lemon available (which nothing else here uses), as well awk and other tools which don't fit well within our windows-side compiles, or.. 2) Download a preprocessed archive that contains only two files (sqlite3.c and sqlite3.h) losing the ability to easily track changes (or make local patches / fixes if necessary) as well as no longer having the shell code. I'll have to download both archives and piece together my own build. Hopefully this doesn't come off as too much of a nag, but the way it was before was quite convenient and the new method seems to have taken the 'preprocessed' notion to the extreme. If this is how it's going to be from now on, I'll just have to adjust, but if there wasn't any specific reason for changing, you can count this as a vote for the 'old' way. :) Cheers... Patrick Bennett ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
