Hi Steve, You raise a fundamental issue that I admit I don't completely understand. What are the differences between linking against a static library versus a framework. If I turned all my static libraries into a framework would the plugin see the static variables in the framework without having to do all the Xcode linking magic?
Thanks, Philip On Jan 2, 2012, at 10:26 AM, Steve Sisak wrote: > At 9:47 AM -0500 1/2/12, Grandinetti Philip wrote: >> So, I can't really define the static variable pointing to my library in the >> plugin. It needs to be defined in the library that handles all the SI >> units. > > Hi Philip, > > This is dusting off brain cells that I haven't used in awhile but, assuming > all the plugins run only in your application, you could put all of the > code/data shared by the plugins into a framework that resides in your > application bundle. > > Your application and your plugins then link against this framework. > > You could use either CFPlugin or NSBundle as Chris suggests. > > The tough part here is all the Xcode magic to get the targets set up > correctly -- I'm currently working out something similar, and will post > results. > > If someone has a recipe for setting this up in Xcode 4 and would be willing > to post it, I'd be interested as well. > > HTH, > > -Steve _______________________________________________ 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 arch...@mail-archive.com
