• 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: "Dalzhim Dalzhim" <email@hidden>
  • Date: Thu, 25 Sep 2008 11:18:48 -0400

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


regards


-Dalzhim


2008/9/25 Michael Ash <email@hidden>

> I would have thought that @loader_path would be the same thing each
> time, namely the path of the plugin binary (minus the last path
> component, of course).
>
> I'm not sure exactly what your problem might be, but if you type 'man
> dyld' you'll find a bunch of debugging environment variables you can
> set which might help you track it down.
>
> 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
>
_______________________________________________

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: "Michael Ash" <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>)

  • Prev by Date: Re: NSMutableData and thread safety
  • Next by Date: How to set up a thread listening to performSelector: messages?
  • 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