Re: linking problem with SDK dylib vs. system dylib
Re: linking problem with SDK dylib vs. system dylib
- Subject: Re: linking problem with SDK dylib vs. system dylib
- From: Jean-Daniel Dupas <email@hidden>
- Date: Fri, 22 Feb 2008 17:12:18 +0100
Le 22 févr. 08 à 17:05, Guillaume Laurent a écrit :
On Feb 22, 2008, at 16:38 , Jean-Daniel Dupas wrote:
You should never add file from the SDK (library, header, ...)
Always use absolute path (/usr/lib) and the Xcode build system will
build the library path according to your SDK root settings.
For exemple, you add the libz.dylib from /usr/lib and select 10.4u
SDK, Xcode will link your product using /${SDK_PATH}/usr/lib/
libz.dylib.
OK, I was completely misguided then :-). Still, I find it a little
annoying than libs aren't any easier to access (the Command-Shift-G
thing is kinda hackish).
Thanks for your help,
There is also an unknown OS X tips usefull for this kind of problem.
In any Open Panel, if you type '/' it will open a little sheet where
you can enter a path.
So, choose "add a file…" in your Xcode project, then in the Open
Panel, type '/' and in the path sheet, enter /usr/lib and press enter.
Now you will just have to choose your library ;-)
_______________________________________________
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