Re: @loader_path and @executable_path
Re: @loader_path and @executable_path
- Subject: Re: @loader_path and @executable_path
- From: Joseph Crawford <email@hidden>
- Date: Mon, 12 Jan 2009 15:12:09 -0500
Please see the message below in black.
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"
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?
Thanks,
Joseph Crawford
On Jan 12, 2009, at 11:47 AM, Joseph Crawford wrote:
I do not know if this is a cocoa question or not, it is an error I
get when I hit build & go
This GDB was configured as "i386-apple-darwin".tty /dev/ttys001
warning: Unable to read symbols for "@loader_path/../Frameworks/
BWToolkitFramework.framework/Versions/A/BWToolkitFramework" (file
not found).
warning: Unable to read symbols from "BWToolkitFramework" (not yet
mapped into memory).
warning: Unable to read symbols for "@loader_path/../Frameworks/
Sparkle.framework/Versions/A/Sparkle" (file not found).
warning: Unable to read symbols from "Sparkle" (not yet mapped into
memory).
I did some googling and found that people used a tool to use
@executable_path rather than @loader_path but I also read that
those values should be the exact same so changing them is not the
optimal change to make.
Does anyone have any idea where I can see / set these values? I
have checked my Xcode Project Build settings, the framework build
settings, etc. and cannot find them.
I also thought it was a project setting so i created the project
again from scratch (it's small) but I still got the error, this led
me to believe that it is an XCode setting so I reinstalled dev
tools and the error still remains.
I did some checking in my build and my Frameworks are under
Contents/Frameworks/*
In my project directory I created a directory called /Frameworks/*
and put the frameworks there. I am not sure if this is the best
way to use a framework by including it in my Bundle but I am not
sure how else to do this. I guess I could just put all external
(non osx frameworks) in a directory on my computer and link them.
I have to mention that these errors do not seem to stop the
frameworks from working when i run the build. Sparkle still does
the updates etc, just a bit odd to have the errors at all.
Any suggestions / feedback would be appreciated.
Thanks,
Joseph Crawford
_______________________________________________
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