Re: @loader_path and @executable_path
Re: @loader_path and @executable_path
- Subject: Re: @loader_path and @executable_path
- From: Dave Dribin <email@hidden>
- Date: Mon, 12 Jan 2009 16:06:05 -0600
On Jan 12, 2009, at 2:12 PM, Joseph Crawford wrote:
I figured out that issuing this command in terminal fixed the issue
for this project.
install_name_tool -change "@loader_path/../Frameworks/
Sparkle.framework/Versions/A/Sparkle" "@executable_path/../
Frameworks/Sparkle.framework/Versions/A/Sparkle" "/Users/jcrawford/
Cocoa/TomTom POI Manager/build/Debug/TomTom POI Manager.app/Contents/
MacOS/TomTom POI Manager"
This is dangerous. Because the string "@executable_path" is longer
than "@loader_path", you are probably overwriting parts of the binary
which could cause subtle but weird problems down the line. Don't do
that. (1)
However my question is since this was only for this one particular
project, any other project will encounter these errors.
Is there a way to make this system wide so that if my build
directory is cleared or another project is created this problem will
not be encountered?
This smells like a bug in gdb, if it's warning for @loader_path but
not @executable_path. Just ignore the warnings and file a bug. The
only proper way to change from @loader_path to @executable_path is to
recompile the frameworks with a different install name.
-Dave
(1) Unless the frameworks were linked with -header-
pad_max_install_names. They probably were not, so hence it's dangerous.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden