difference between frameworks and plugins
difference between frameworks and plugins
- Subject: difference between frameworks and plugins
- From: Jesse Grosjean <email@hidden>
- Date: Wed, 2 Feb 2005 16:56:23 -0500
I'm looking for pointers on the difference between cocoa plugins and
cocoa dynamic frameworks.
What I would like to do is allow one plugin to treat (have access to
the symbols at build time) another plugin as if that plugin were a
framework. Is this possible or is there some fundamental difference
between plugins and frameworks that makes doing this impossible.
Right now I can have one plugin talk to another by using
NSClassFromString and performSelector, but I would like to set things
up so that one plugin can use the symbols defined by another plugin and
so that I get some type-checking at compile time. Is this possible, any
thoughts on how best to setup the build environment to support this?
A couple of questions.
To create my plugins I'm using "Add New Target" and I'm choosing a
Cocoa/Loadable Bundle target type. When I then go and select the target
in xCode and choose "Get Info" I'm surprised to see that the "Library
Style" build setting is set to "Static" by default. Is that correct? I
would have expected the style to be "Bundle". Loading the plugin seems
to with any setting (static, bundle, or dynamic), I'd just like to
understand the difference, and if possible use the value that would let
me link one plugin into another.
Right now I'm able to add one plugin to another plugins "Frameworks &
Libraries" build phase. But when I try to compile I get this warning:
Dependency analysis: warning: skipping file 'MyPlugin.plugin'
(unexpected file type 'file' in Frameworks & Libraries build phase)
Is there anyway to get around this?
Thanks for any help.
Jesse
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden