On 29 November 2010 10:37, Murray Cumming <[email protected]> wrote: > On Sat, 2010-11-27 at 15:57 +0100, Vivien Malerba wrote: >> On 27 November 2010 15:42, Johannes Schmid <[email protected]> wrote: >> > Hi! >> > >> > I was wondering why the default in libgda is to use the embedded sqlite. >> > As distributions usually have security updates for sqlite very quickly >> > most of them use their system-installed sqlite anyway (debian/ubuntu). >> > >> > Is there a reason why the system sqlite isn't used by default when it is >> > compiled with the necessary flags? >> >> No, there is not. I guess the configure.ac file can easily be changed >> to have the system version selected if available. However, doing this >> would make all the packagers update their scripts, which is not a good >> idea. > > So is there ever a reason to use the copy of the sqlite source code > that's in libgda?
SQLite has many compilation options, and Libgda requires some of them. The configure script checks that the system installed SQLite has the required ones before using it. On Windows, the embedded version is always used. Also the embedded version is always used for the SQLCipher provider as SQLCipher only exists AFAIK as a source code patch. > > If the installed one needs to have been built with specific options, how > can we check for that? The tests are in the configure.ac file: * the sqlite3_table_column_metadata() symbol must be present * the version must be >= 3.6.11 * also it is recommended that the system install of SQLite be compiled with the SQLITE_THREADSAFE flag (this check is not enforced but it should be). Regards, Vivien _______________________________________________ gnome-db-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-db-list
