Re: Plugin Framework
Re: Plugin Framework
- Subject: Re: Plugin Framework
- From: The Amazing Llama <email@hidden>
- Date: Tue, 7 Oct 2003 08:50:42 -0700
It builds in this order:
MyFoundation.framework
MyPlugins.framework //requires the MyFoundation.framework
First.plugin //requires both of the above frameworks
Next.plugin //requires both of the above frameworks
Keen.app //requires the frameworks, includes the plugins
Anytime a framework is included before the app is built, I get the
warning, because the linker can't access to the frameworks at the path
specified, as it's in the app bundle, which isn't built yet.
So yes, the order is correct (I think), but all of my plugins look for
the framework in the app, which is built last, which is why I think
there's gotta be a simple way around this.
On Tuesday, October 7, 2003, at 04:51 AM, Olivier Destrebecq wrote:
did you try to change the order of the targets in your super target
(the one that include all the other, so that the framework is built
first?
Olivier
On Oct 5, 2003, at 8:58 PM, The Amazing Llama wrote:
I'm trying to build an application using a plugin structure, with all
plugins' primary classes being subclasses of a superclass I provide
in a framework. All targets (framework, plugins, and application) are
build in the same project.
This means that the plugins must link against the Framework, and both
plugins and framework are copied into the app bundle by the
application target's build settings.
Everything builds and works, but for each plugin, I get the warning:
can't open dynamic library:
@executable_path/../Frameworks/FrameworkName.framework/Versions/A/
FrameworkName
Which makes perfect sense, as the framework is not in the executable
until after the app is built, which is after all the plugins are
built (Well; it almost makes sense; my explanation only makes sense
on clean rebuilds).
I have tried to search Mamasam for a solution, but it doesn't like
apostrophes ("can't") or punctuation ("@executable_path") in it's
search strings.
While this doesn't actually seem to cause any problems, it's
annoying. There has to be a way around this, but I can't figure it
out. Any suggestions?
Seth A. Roby The Amazing Llama < mail or AIM me at tallama at mac
dot com>
"Life is like an exploded clown. It's really funny until you figure
out what just happened."
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
Seth A. Roby The Amazing Llama < mail or AIM me at tallama at mac dot
com>
"Life is like an exploded clown. It's really funny until you figure out
what just happened."
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.