Re: Xcode uses "SDK Path" instead of my "Library Search Paths" ?
Re: Xcode uses "SDK Path" instead of my "Library Search Paths" ?
- Subject: Re: Xcode uses "SDK Path" instead of my "Library Search Paths" ?
- From: Jerry Krinock <email@hidden>
- Date: Mon, 22 May 2006 10:53:24 -0700
- Thread-topic: Xcode uses "SDK Path" instead of my "Library Search Paths" ?
on 06/05/21 23:50, Chris Espinosa at email@hidden wrote:
> The best thing to do here is either to build against the copy of sqlite3 in
> your Intermediates directory, or to add a symlink from
> /Developer/SDKs/MacOSX10.4u.sdk/usr/local/lib to /usr/local/lib.
Thank you, Chris. Adding this symlink to my Xcode installation allowed MyApp
to build without errors, but MyApp still used Tiger's sqlite3.dylib at
runtime, and after reading some documentation I think this is because I had
started out down the wrong "path" before asking for a solution yesterday.
Let's step back. I desire a private dylib embedded in MyApp. Yesterday, in
my sqlite3.dylib project, I had forgotten to change "Installation Directory"
to "@executable_path/../Libraries". (Previously, this had been
"/usr/local/lib" which is apparently what Xcode used to concoct that
"nonsense" path.)
So, I've now done this:
1. removed that symlink in my Xcode installation.
2. in my sqlite3.dylib project, changed "Installation Directory" to
"@executable_path/../Libraries".
3. hit "Build" in sqlite3.dylib. Result: Successful.
4. hit "Build" in MyFramework. Result: Successful.
5. hit "Build" in MyApp: Result, during Linking:
/usr/bin/ld: warning can't open dynamic library:
@executable_path/../Libraries/libsqlite3.dylib
referenced from:
/Users/jk/Documents/MyApp/../MyFramework/build/Release/MyFramework.framework
/MyFramework
followed by consequent "undefined symbol" errors.
Now, I have a Shell Script Build Phase which copies my new libsqlite3.dylib
to MyApp's package. It is definitely there, at:
Contents/Libraries/libsqlite3.dylib
I have compared the spelling of the missing path in the error message with
that of the actual path many times, and it looks perfect to me. The two
"dots" get it up out of MacOS and into Contents, then it should go down into
Libraries and find libsqlite3.dylib.
Why can't Xcode open it?
Jerry
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden