Do you mean libsqlite.a?
Yes, exactly. (typo)
Do you have libsqlite3.dylib (or something like it) in /usr/local/lib? ... alternatively, try otool -L on the compiled binary produced by Xcode.
If you are dynamically linking SQLite, try building it statically (see the list archives -- I posed how to do this a few days ago). It may be that you are running into a dynamic linking issue.
No, the only items I have in /usr/local/lib are: charset.alias libsqlite.a libsqlite.la pkgconfig/
This is the output from otool:
tom$ otool -L /Users/tom/Documents/Externals/SQLite/build/SQLite.bundle/Contents/ MacOS/SQLite
/Users/tom/Documents/Externals/SQLite/build/SQLite.bundle/Contents/ MacOS/SQLite:
/System/Library/Frameworks/Carbon.framework/Versions/A/Carbon (compatibility version 2.0.0, current version 128.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 71.1.1)
Which means it's statically linked, right?
I used --enable-static (and --disable-shared) when I ran the configure script, which seems to be what you suggested in your earlier post.
The bundle works perfectly on my server Mac, which has never even touched sqlite before. :-)
Any more ideas? Thanks a lot.
Tomas Franzén Lighthead Software http://www.lightheadsw.com/
