Re: IB Plugin won't load library nib templates
Re: IB Plugin won't load library nib templates
- Subject: Re: IB Plugin won't load library nib templates
- From: "Brent Gulanowski" <email@hidden>
- Date: Thu, 3 Jan 2008 12:03:27 -0500
On Jan 2, 2008 6:46 PM, Ricky Sharp <
email@hidden> wrote:
On Jan 2, 2008, at 3:50 PM, Brent Gulanowski wrote:
> I have followed the docs and looked at samples and successfully
> created IB3 plugins starting with the project template.
>
...
Search the list archives; this was covered in the recent "Problem
loading IB plugin" thread.
I did refer to the previous threads but it was difficult trying to determine if the answer was really there: there were multiple issues being discussed simultaneously, plus the problem I seem to be having shouldn't be happening:
>
> The framework target specifies the installation location as /Library/
> Frameworks/ - I was trying to load the plugin from the build folder
> in my project, without putting a copy in the standard location. I
> should have thought of this before - this has come up in previous
> projects. It's a common reason for projects including loadable
> bundles to stop working outside of Xcode if the bundles are kept
> inside the application bundle. I have had to change the
> installation location from /Library/Frameworks to
> @executable_path/../Frameworks on a regular basis.
Hey Rick -
You nailed it. This works when you hit build and run in Xcode because
Xcode sets the DYLD_FRAMEWORK_PATH environment variable before
launching an executable to debug (IB). If you want to quickly load
your built plug-in, you can either install a symlink from /Library/
Frameworks/<YourFramework>.framework back to your built framework, or
you can launch
IB from the terminal with DYLD_FRAMEWORK_PATH set to
your built products directory. The symlink is probably most convenient
here.
As I mentioned in my last post, I wasn't getting complaints about not finding the frameworks when I launch IB via Xcode/gdb, so it seemed to me that that wasn't the problem. Again, I wasn't getting *any* console errors and the plugin was loading fine (when it fails to load it is *not* supposed to be listed in the preferences). It just doesn't show anything in the Library window.
I will add that trying to solve it by working with IB on its own, the symlink suggesting here doesn't work. IB is still looking for dependent frameworks in @executable_path/../Frameworks. I'll try the
DYLD_FRAMEWORK_PATH solution if I can figure out how to set it.
This is slightly complicated in that the framework in which my plugin resides depends upon a number of other frameworks, all of which are meant to be embedded in the application bundle. But when I copied all of the frameworks into ~/Library/Frameworks I didn't get any console errors (though the plugin classes are still not visible in the Library window).
Sorry for any difficulty explaining myself clearly or if I have missed exactly which solution is the solution to my problem in the aforementioned previous discussion.
TIA,
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden