Well I basically did the following, but not sure it's optimal: 1) Took 3.3.17 amalgamation 2) Took shell.c from 3.3.17 full distribution, and made a target that just uses sqlite3.c and shell.c to get the command line tool 3) Took whatever I had in my old makefile for compile flags and added them for compiling sqlite3.c in my project
An extra step was needed: 1) Apparently 3.3.17 needs libdl, where 3.3.8 seemingly didn't, so I had to make some adjustments. Not that it's all that hard to figure the above out, but just wanted some perspective on the "recommended" approach, since I couldn't find any docs or list emails regarding building the shell using the amalgamation, and things might change so that what I'm doing now may no longer "work." Thanks, Brett -----Original Message----- From: Brett Keating [mailto:[EMAIL PROTECTED] Sent: Saturday, June 09, 2007 9:43 AM To: sqlite-users@sqlite.org Subject: [sqlite] Amalgamation questions Hi, I am interested in upgrading my sqlite3, and the amalgamation looks like an interesting option. However I have some questions. 1) The page says with 3.3.18, the amalgamation will be available for direct download. Is 3.3.18 not available yet? It's not on the download page. If it's not I will generate it from 3.3.17... just want to make sure I have to do that :) 2) With the old way of configuring, generating and building the sqlite library, I have a makefile that builds both a linkable library as well as an installable command-line tool. With the amalgamation, I no longer need to build the linkable library because I can directly drop it into my project... but then what is the recommended way to also build the command-line tool and install it, under this paradigm? 3) Is there a set of compile-time options that I'd have to include in my project makefile (which would now include the amalgamation of sqlite), that would otherwise have been in sqlite's own makefile under the old paradigm? Thanks! Brett ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------