• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: @loader_path and @executable_path
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: @loader_path and @executable_path


  • Subject: Re: @loader_path and @executable_path
  • From: Dave Dribin <email@hidden>
  • Date: Mon, 12 Jan 2009 16:00:04 -0600

On Jan 12, 2009, at 10: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).

These are just debugger errors. This is most like due to those frameworks being compiled in Release mode with their debug symbols stripped. It should not affect debugging of your own application.


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.

For an application, they resolve to the same thing.

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.

They are set in the frameworks project, not yours. So if you're linking to pre-built versions of Sparkle and BWToolkit, there are no settings in your app that affect this.


In general, @loader_path is preferred over @executable_path, as it allows embedded frameworks to work in both an executable and a bundle, plugin, or sub-framework. The only downside is that @loader_path requires 10.4 or newer. If you're on 10.5 or newer, @rpath is even better than @loader_path.

-Dave

_______________________________________________

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


  • Follow-Ups:
    • Re: @loader_path and @executable_path
      • From: Brandon Walkin <email@hidden>
References: 
 >@loader_path and @executable_path (From: Joseph Crawford <email@hidden>)

  • Prev by Date: Re: Xcode-like "Groups & Files" view: NSTreeController and/or core data?
  • Next by Date: Re: Disabled button looks like enabled
  • Previous by thread: Re: @loader_path and @executable_path
  • Next by thread: Re: @loader_path and @executable_path
  • Index(es):
    • Date
    • Thread