On Tue, Apr 15, 2008 at 5:15 PM, Thomas Backman <[EMAIL PROTECTED]> wrote: > Now, that means that the three plugins, each with only 100-150 lines of > code, need 4MB worth of frameworks... Is there a way to get around this > without making it ugly, to include the frameworks *once*?
Build your frameworks with the @executable_path macro in the install path setting, and copy them into your app bundle's Frameworks directory as part of the app target build. People writing plugins can then link against these frameworks, but their plugins will still work, regardless of where your app loads them from (Application Support, its internal Plug-Ins directory, anywhere). See < http://developer.apple.com/documentation/DeveloperTools/Conceptual/DynamicLibraries/Articles/DynamicLibraryDesignGuidelines.html#//apple_ref/doc/uid/TP40002013-SW21 > for more details. --Kyle Sluder _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
