Re: SQLite Version Issues

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dennis Lee Bieber wrote:
> 	Ah, yes... the nice, user-friendly, Macintosh... The McDonald's of
> computers -- Have it our way, we know what you want...

I now remember what the solution was.  You had to rename your own copy
of sqlite to anything else and link with the different library name.
That way you will get the SQLite you want.

As to what they did in this case, Apple provides SQLite as a system
library and ensure it is used as such.  The version they use as well as
the default does not allow two different versions in the same process
and many Mac system libraries are using SQLite.  There is no right
answer about what to do in this case, although their solution is
acceptable.  (They have also modified their SQLite to do locking in a
way that is better for the Mac).

> 	And people think M$ Windows is hard to configure

This has nothing to do with configuration and everything to do with
software development and what happens when you do things at odds with
the core system libraries.  As a developer you always have to jump
further away through various hoops.  (Eg try using a different
kernel32.dll/gdi.dll on Windows or libc/GTK on Linux while loading lots
of other things into your process.  It can always be done, but as a
developer you have to go that extra mile.)

For the record I wouldn't have done what Apple did.  If I wanted SQLite
as a core system service I would have changed the shared library and
function names so they could never clash with the normal SQLite.

Roger
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHR9gjmOOfHg372QQRAnIQAJsGdI8uIURWpLlcc01qYxC1bp8HlQCgxsTo
pEvO2/XiSj5tSLXQ4V1qsDU=
=BH3J
-----END PGP SIGNATURE-----