Re: question on bundles and frameworks...
Re: question on bundles and frameworks...
- Subject: Re: question on bundles and frameworks...
- From: Mike Ferris <email@hidden>
- Date: Wed, 11 Dec 2002 09:29:58 -0800
#2 is probably the way to go. You can embed the framework inside the
app to keep things self-contained. This makes it slightly less
convenient for your bundles to link the framework since they have to
dig down inside the app wrapper to find it.
There's documentation on the (currently unfortunately complicated) way
to build a framework embedded inside an application as part of the PB
documentation.
If you build the common stuff into each plugin be sure not to export
any of the common stuff or else rename it in each bundle to avoid name
conflicts.
A third option is to put the common stuff in your app and then have the
plugins "link against" the application using the -bundle_loader linker
option (be sure to add a "-S" to the linker options of the app as well
if you do this).
Really, though, the cleanest approach is to put the common stuff in a
framework.
Mike
Begin forwarded message:
From: Steve Mykytyn <email@hidden>
Date: Tue Dec 10, 2002 3:19:31 PM US/Pacific
To: email@hidden
Subject: question on bundles and frameworks...
i can't decide if this is obvious or not after considerable searching
- any help would be appreciated.
I have a Cocoa app, call it A, that load several bundles, call them B,
C, D, and E, each of which contains several plug-ins that all conform
to the same protocol. It is likely that in the future there will be
more such bundles. The bundles B, C, D, and E are loaded at run-time.
There is a small set of C functions that it would be nice for B, C, D,
and E to have access to. Not a huge amount of code. Would it be best
to:
1. build them directly into each bundle B, C, D, and E?
2. build them into a framework F, which could be accessed by B, C, D,
and E, and the application A as well?
It's not clear to me how to do #2 in a non-dopey way.
_______________________________________________
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.
_______________________________________________
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.