Re: dyld issues with library not in standard location
Re: dyld issues with library not in standard location
- Subject: Re: dyld issues with library not in standard location
- From: Andrea -XFox- Govoni <email@hidden>
- Date: Thu, 20 Oct 2005 18:07:13 +0200
Graham Hemingway ha scritto:
> Peter,
> Is using install_name_tool something I have to run after I have
> compiled everything or is it something I can set up in XCode?
You can build your library with the -install_name option.
To do this add to your OTHER_CFLAGS library's build setting the option
-install_name @executable_path/../relative/path/to/lib.dylib
This should build the library with the given install name and when you
build the app it should record the given path and use it to find the
library at launch time.
OR
You can add a final Shell Script Build Phase to your library's target
and call the install_name_tool command with the -id option to modify the
library's install name as noted above.
OR
You can add a final Shell Script Build Phase to your app's target and
call the install_name_tool command to modify the path where it searches
for the library.
There is an Apple developer article that explains quite well all the
dynamic libraries related issues:
<http://developer.apple.com/documentation/DeveloperTools/Conceptual/DynamicLibraries/>
--
Andrea "XFox" Govoni
ICQ UIN: 43488185
AIM/iChat: email@hidden
Yahoo! ID: xfox82
Skype Name: draykan
PGP
KeyID: 0x212E69C1
Fingerprint: FBE1 CA7D 34BE 4A53 9639 5C36 B7A0 605F 212E 69C1
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________
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