On Jul 23, 2009, at 10:50 PM, Jay A. Kreibich wrote: > On Thu, Jul 23, 2009 at 09:46:24AM -0400, Wilson, Ron P scratched on > the wall: > >> I think the OP just has the wrong expectations. > > Yes, and no. While SQLite doesn't have a one-click-to-install > download, I have to agree that the current build and distribution > state of SQLite is... let's just say "less than ideal." I've been > writing a lot of documentation on just this issue, and unless you > want a perfect vanilla install, there are definitly a lot of hoops > you have to jump through compared to most open-source projects of > similar design. > > A few versions ago we transitioned from a traditional UNIX style > project, complete with "configure" script, to having the amalgimation > be the "standard" distribution. I've always felt like that > transition is imcomplete, and we've never gotten back to where we > were before. > > The amalgimation works well enough if what you want is mostly > defaults. The issue is that, while you can change a few of the > #defines for numric defaults, most of the more interesting build > options won't work with the amalgimation. Only that's it. As the > website clearly states, there is no other supported option. > no suppored "by the file"
I think it's just the SQLITE_ENABLE_UPDATE_DELETE_LIMIT feature and some of the SQLITE_OMIT_XXX symbols that won't work with the amalgamation version. I haven't tried though, so could be wrong there. There is an amalgamation package that includes a supported configure script. "./configure && make install" and you're away. You can specify compile time options via the CFLAGS environment variable. The problem with the configure script in the full source tree distribution is that it is complex and nobody really seems to understand it. Hence "unsupported". _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
