sqlite on MacOS X

[cormullion]

Just wondering whether sqlite is correctly configured on MacOS X Tiger (10.4.2)?



sqlite.lsp says:



;; Mac OSX / Darwin

   (= (& 0xF (last (sys-info))) 3) (set 'library "/usr/local/lib/libsqlite3.0.dylib")



but 'find' shows sqlite in the following locations:



/usr/bin/sqlite3

/usr/lib/libsqlite3.0.8.6.dylib

/usr/lib/libsqlite3.0.dylib

/usr/lib/libsqlite3.dylib

/usr/lib/php/DB/sqlite.php

/usr/lib/sqlite3

/usr/lib/sqlite3/libtclsqlite3.dylib

/usr/share/man/man1/sqlite3.1

/usr/share/newlisp/sqlite.lsp

/usr/share/newlisp/sqlite3.lsp



Error message is:



dlopen(/usr/local/lib/libsqlite.so, 9): image not found

problem loading library in function import : "/usr/local/lib/libsqlite.so"

[Lutz]

Interesting, how did you installl SQLite3 ?



Lutz

[cormullion]

Interesting, how did you installl SQLite3 ?



Lutz

I don't think I did... Isn't it part of MacOS 10.4 (Tiger)?

[Lutz]

Thats probably why we see the difference. We will change to usr/lib then.



Lutz

[cormullion]

I read somewhere that 3rd party non-system tools should be installed in /usr/local rather than /usr/bin? Perhaps this is one of those issues that Unix gurus argue about... :-)

[Dmi]

about /usr/local: Simply usefulness.

The tons of files under /usr on most systems are well-maintained by package manager.

If you will place there your files by "make install" or "cp", then sometimes  you'll spent many time with maintaining your own files inside all the trash that sits in /usr :-)



In other hand, if you prepare/install a system package, then it's ok to place it in /usr (or everywhere you want ;-)