Re: Providing application resources to a Plugin
Re: Providing application resources to a Plugin
- Subject: Re: Providing application resources to a Plugin
- From: j o a r <email@hidden>
- Date: Mon, 21 Aug 2006 22:28:37 +0200
On 21 aug 2006, at 20.59, Eric Czarny wrote:
Say, for instance, I have a blogging application that should support
multiple blogging programming intefaces. If I were to implement each
blogging API as a plugin, how could I provide a common resource
(such as an
XML-RPC client) without linking them directly to the framework?
Meaning, I
would like to have my application link to (and include within its own
bundle) the XML-RPC framework. Could I simply include the XML-RPC
headers
within a Plugin.framework, along with the plugin's protocol and
abstract
class?
If both application and plugins needs access to the functionality
provided by your XML-RPC framework, why not allow both application
and plugins to link to it? While it's possible to do what you suggest
(by suppressing linker warnings), it's a less elegant approach.
Build the framework with the "@executable_path/../Frameworks" install
path build setting and include it in the application bundle. This
will allow both application and plugins to find it when the
application is running.
j o a r
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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