On Feb 11, 2007, at 3:17 PM, Peter K. Stys wrote:
could someone please briefly explain the diff between a dylib and a bundle (I gather the latter is a collection of libs?), and why you'd use one over the other.
There are two issues that are important: private name space and loading in memory.
A dylib is a naked executable, while a .plugin or a .bundle is a folder package containing a naked executable. These naked executables are different. a bundle or plugin executable are derived from a dylib. The difficulty with a dylib is to obtain a private copy, particular in REALbasic, but probably in other environments too. There are no such problems (obtaining a private name space of an executable) with bundles.
Note that you can put a bundle package in the Plugins folder and REALbasic will load it correctly, however in a slightly non- conventional way. REALbasic will traverse the packaged bundle, in doing so it will encounter the Contents folder first, and then tries to load the Info.plist (will fail, RB reports that to the console), also encounters the MacOS folder and loads the executable therein.
This non-conventional mechanism, crawling into the package, also allows plugin developers to grab the bundle executable and stick it into the rbx virttual volume. No need to provide an Info.plist, and the upshot of a bundle executable over a dylib is that RB will load the bundle in memory (does not write out to a temporary file).
Alfred _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
