> Le 15 déc. 2014 à 21:36, Greg Parker <gpar...@apple.com> a écrit : > > >> On Dec 15, 2014, at 11:02 AM, Jean-Daniel Dupas <mail...@xenonium.com> wrote: >> >>> Le 15 déc. 2014 à 19:45, Fritz Anderson <fri...@manoverboard.org> a écrit : >>> >>> - As is typical of ObjC plugins, the classes are packaged in a dynamic >>> library; and as is typical, the library is wrapped in a package directory, >>> which your application has registered with Launch Services as a package, of >>> a certain type and edit/view/associate relationship to your application. >>> I'm sure this is so in your case, as plugins typically need to carry >>> resource files. >> >> Just for the record, typical Obj-C plugins are packaged in loadable bundle >> (MH_BUNDLE), which are a different binary object kind than dynamic library >> (MH_DYLIB). > > MH_BUNDLE is no longer typical. The only advantage of MH_BUNDLE is that you > might be able to unload it, but you probably shouldn't try. Feel free to use > MH_DYLIB for all of your plugin needs.
It is typical in the sense that Xcode defaults to mach-o type bundle when creating a plugin project and most (if not all) Apple provided plugins are bundle (as are most third party plugins). > (libobjc prevents unloading of any MH_DYLIB containing Objective-C metadata. > It does not summarily disallow unloading of MH_BUNDLE, but there's a long > list of caveats that make bundle unloading unusable except in rare > situations.) _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
