Problem with plugin architecture development and subclass into bundles
Problem with plugin architecture development and subclass into bundles
- Subject: Problem with plugin architecture development and subclass into bundles
- From: Daniele Margutti <email@hidden>
- Date: Wed, 24 Nov 2010 18:29:47 +0100
Hello List,
I need to make a plug-in based application.
The most common way is to define a protocol that each plugin (bundle)
principal class must follow.
However for some reasons I need to use subclasses instead of protocol.
So I've a PluginLoader class and a BasePluginClass. This class is the
superclass of each plugin's principal class. It contains some methods
and bla bla.
This is my environment:
http://i.imgur.com/PLJgm.png
The main problem is at runtime when I get this error:
Class MKAbstractUITool is implemented in both
/Users/malcom/Desktop/MyApp/build/Debug/MyApp.app/Contents/MacOS/MyApp
and /Users/malcom/Desktop/MyApp/build/Debug/MyApp.app/Contents/PlugIns/UITools/iOS/MKiOSTabBar.MyApptool/Contents/MacOS/MKiOSTabBar.
One of the two will be used. Which one is undefined.
This because I've imported my BasePluginClass (named MKAbstractUITool)
both in main app and my plugin.
That's not only a warning but a problem because when I try to load a
(valid) plugin this check fail
if ([prinClass isSubclassOfClass:[MKAbstractUITool class]] == NO)
and return NO.
(and my prinClass is a subclass of that).
I've also tried to use @class MKAbstractUITool but it return error
linking (cannot found MKAbstractUITool...).
It's the same using HEADER_SEARCH_PATH instead of importing .h and .m
of MKAbstractUITool into my bundle project.
And it's the same importing only the .h.
Any idea?
Thanks
_______________________________________________
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