Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Circular confusion with Cocoa bundles

On Jun 30, 2004, at 4:38 PM, Mark Dalrymple wrote:

Greetings,

I'm developing a Cocoa application that is plug-in driven. I have an Objective-C class, BWTrackerPlugin, that provides some stuff (instance variables, utility methods, and plugin API) common to all plugins, and Individual plugins are composed of a class that inherit from this class. Each plugin is a "Cocoa Bundle" target in the same Xcode project as the main app.

If I don't include BWTrackerPlugin.m in the plugin target, I get this build error:

ld: Undefined symbols:
.objc_class_name_BWTrackerPlugin

If I do include BWTrackerPlugin.m in the plugin target, I get this runtime warning:

objc: Both (application) and (plugin) have implementations of class BWTrackerPlugin.
objc: Using implementation from (plugin)

I know I'm missing something Obvious, but I don't see an Obvious Xcode switch which would let me link the plugin without needing the superclass file.

Look for -bundle_loader in the ld man page and in the Masamam archives.

It's what you're looking for probably.
_______________________________________________
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.

References: 
 >Circular confusion with Cocoa bundles (From: Mark Dalrymple <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.