Re: codesign vs. install_name_tool
Re: codesign vs. install_name_tool
- Subject: Re: codesign vs. install_name_tool
- From: Jeff Johnson <email@hidden>
- Date: Thu, 23 Feb 2012 20:54:45 -0600
On Feb 23, 2012, at 11:53 AM, Dallman, John wrote:
>> Use @rpath/mylib.dylib for the install name. Then application developers
>> can use LD_RUNPATH_SEARCH_PATHS in their build settings to find your library.
>
> This looks interesting, but I don't speak Xcode IDE - my sight is quite poor,
> and IDEs don't work well for me.
>
> https://developer.apple.com/library/mac/#documentation/DeveloperTools/Conceptual/DynamicLibraries/100-Articles/RunpathDependentLibraries.html#//apple_ref/doc/uid/TP40008306-SW1
>
> If I'm following you correctly, LD_RUNPATH_SEARCH_PATHS is a macro in Xcode that
> gets expanded to one or more -rpath options to ld when building the executable?
> Those rpath options store strings in the executable for the dylamic loader to
> use at load time? If so, then yes, I should be able to solve the problem that way.
>
> Thanks!
I wouldn't call it a macro exactly, but the behavior you describe is essentially correct. The paths in LD_RUNPATH_SEARCH_PATHS get passed to the compiler as -F options and to the linker as -rpath options.
-Jeff
_______________________________________________
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