• 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: What does @loader_path refer to when loading ibplugins from a linked-in framework?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: What does @loader_path refer to when loading ibplugins from a linked-in framework?


  • Subject: Re: What does @loader_path refer to when loading ibplugins from a linked-in framework?
  • From: "Michael Ash" <email@hidden>
  • Date: Thu, 25 Sep 2008 12:04:47 -0400

On Thu, Sep 25, 2008 at 11:18 AM, Dalzhim Dalzhim
<email@hidden> wrote:
> Hello Michael,
>
> I would have also thought that @loader_path would be the same thing no
> matter how I load my ibplugin into interface builder and maybe it is in fact
> the case, although this is the only thing that I haven't successfully
> investigated that I can think of up to now in order to solve my problem.  As
> I explained previously, the ibplugin I have built successfully loads up in
> Interface Builder when I manually add it through the Plugin tab of the
> Preferences window.  Although if I do not load it up manually and that I try
> to have Interface Builder load it dynamically by opening a nib file in a
> xcode project which links against a framework which includes my ibplugin in
> its resources directory, the plugin never loads up and I cannot seem to find
> any errors to help me find the source of the problem.
>
> I have looked at the man page for dyld and I have found some documentation
> in the Dynamic Library Programming Topics.  Although I tried using the
> DYLD_PRINT_BINDINGS environment variable I didn't find where this logging is
> being done.  Nothing appeared on the console after I ran interface builder
> and repeated the usual process:
>
> DYLD_PRINT_BINDINGS=1
> cd /Developer/Applications/Interface\ Builder.app/Contents/MacOS
> ./Interface\ Builder

This just sets a shell variable. IB won't see it. Either export it:

export DYLD_PRINT_BINDINGS=1

Or set it as part of running the binary:

DYLD_PRINT_BINDINGS=1 ./Interface\ Builder

Mike
_______________________________________________

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: What does @loader_path refer to when loading ibplugins from a linked-in framework?
      • From: "Dalzhim Dalzhim" <email@hidden>
References: 
 >What does @loader_path refer to when loading ibplugins from a linked-in framework? (From: "Dalzhim Dalzhim" <email@hidden>)
 >Re: What does @loader_path refer to when loading ibplugins from a linked-in framework? (From: "Michael Ash" <email@hidden>)
 >Re: What does @loader_path refer to when loading ibplugins from a linked-in framework? (From: "Dalzhim Dalzhim" <email@hidden>)

  • Prev by Date: Re: How to set up a thread listening to performSelector: messages?
  • Next by Date: Filtering an NSArrayController using a to-many relationship
  • Previous by thread: Re: What does @loader_path refer to when loading ibplugins from a linked-in framework?
  • Next by thread: Re: What does @loader_path refer to when loading ibplugins from a linked-in framework?
  • Index(es):
    • Date
    • Thread