Re: Creating a subclass of an *unknown* object
Re: Creating a subclass of an *unknown* object
- Subject: Re: Creating a subclass of an *unknown* object
- From: Chris Hanson <email@hidden>
- Date: Wed, 15 Jun 2005 10:26:08 -0700
On Jun 15, 2005, at 7:44 AM, Stefan Schüßler wrote: Normally, this is done by having a common framework that both the application and the plug in link against
If you don't have a framework to link against you can add "-flat_namespace -undefined suppress" to "Other Linker Flags" in you build settings.
However, your plugin will crash if the symbols are not defined in the host application.
You generally want to avoid using -undefined suppress as it will leave error conditions (unresolved non-weak-linked symbols) undetected.
If you're building a bundle that needs access to symbols from its host application, you should specify the host application's executable as the bundle's loader via the -bundle_loader linker flag. In Xcode 2.1, this is exposed via the "Bundle Loader" build setting, prior to Xcode 2.1 you'll have to set this in "Other Linker Flags".
This way you'll still get errors for symbols that are truly undefined, while also being able to resolve symbols from the host application in your bundle.
-- Chris
|
_______________________________________________
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