Re: Organizing an Xcode template and frameworks for plugin development kit
Re: Organizing an Xcode template and frameworks for plugin development kit
- Subject: Re: Organizing an Xcode template and frameworks for plugin development kit
- From: Brent Gulanowski <email@hidden>
- Date: Sat, 18 Sep 2004 22:55:50 -0400
On Sat, 18 Sep 2004 10:41:55 -0400, Rick Hoge <email@hidden> wrote:
>
> I am trying to put together a plugin developers kit for our Cocoa
> application. The kit would consist of an Xcode template and a couple
> of frameworks. In our app plugins are subclassed from a base class
> that is provided in one of the frameworks. Building a plugin target
> produces a loadable bundle that is discovered automatically by the app
> at launch time if installed in the correct location.
>
> I'm trying to figure out the correct way to ship these components - the
> obvious thing would be to wrap them in an installer package and put the
> Xcode template under ~/Library/Application Support/Apple/Developer
> Tools/Project Templates/MyApp/MyAppPlugin/ - what I'm not sure about
> is how exactly to install the framework bundles. The Apple docs give a
> good overview of were to put the headers and framework API
> documentation, but I'm not sure about the appropriate install location.
>
> Possible options seem to be:
>
> 1) have the plugin projects point to the frameworks that are shipped
> anyway inside the bundle of the main application
>
> 2) include copies of the frameworks (which aren't huge) inside the
> Xcode template
>
> 3) when the user/developer runs the installer for the Xcode template
> the frameworks get installed somewhere under ~/Library/ or /Library/
> and the template is configured to look there
>
> If anyone could comment on the relative merits of these options or
> other better options I'd be very grateful!
I'm pretty confident that the SDK only needs to have the interface
files (headers) for the plug-in code to compile correctly. If your app
has the library code loaded (I'll assume such), then when the plug-in
is loaded dyld should resolve the references OK. The framework code
isn't needed during compile time, only run time.
Now if the plug-in developer wants to write test tools/apps then
that's another story. But in any case, as long as the framework is
somewhere on the framework search paths, I think you're fine.
I'm sure I'll be corrected if I'm wrong on some point.
--
Brent Gulanowski
http://www.boredastronaut.com
_______________________________________________
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