-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The preferred solution for most SQLite using developers is to include a
private copy of SQLite. You just add the single amalgamation source file
to your project and are no longer at the mercy of whatever goes on on the
platform.
For my own project I actually go a step further (by default). I #include
the amalgamation into another C file that does all the interfacing with
SQLite. You can do various #defines that makes all the SQLite code be
static - ie none of it leaks outside of that file. This will do the trick:
#define SQLITE_API static
#define SQLITE_EXTERN static
This approach is extremely robust and your very private copy of SQLite
will coexist with any other SQLite dynamically loaded into the same
process even if they are completely different versions with different
compilation options.
This was about the only way of getting things to work on MacOS. CoreData
uses SQLite and ends up being loaded into almost every process.
Additionally the process loading mechanisms will generally override
whatever mechanisms you use to point it at a different SQLite library and
force usage of the system one anyway.
Roger
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iEYEARECAAYFAk7uX5QACgkQmOOfHg372QTHZwCeJtVW8N7J9EU+fu8vnJQAFa+z
4zYAn1mdKOnCrbsvZmbPhk013nMabBwv
=bDrI
-----END PGP SIGNATURE-----
_______________________________________________
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
