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 PROTECTED]>

> 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 (Cocoa-dev@lists.apple.com)
>
> 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:
> http://lists.apple.com/mailman/options/cocoa-dev/dalzhim.mlist%40gmail.com
>
> This email sent to [EMAIL PROTECTED]
>
_______________________________________________

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to [EMAIL PROTECTED]

Reply via email to