From what I understand, you can either create a module which you can
dynamically load (.bundle) or one which you can dynamically link
(.dylib), but not both.
From what I understand, there's no difference between a library
loaded automatically and one loaded explicitely. Both are loaded at
runtime, anyways.
The only difference seems to be the location of the Bundle (in the
dynamic linker's default paths or not) and perhaps a flag in the
Info.plist.
Also, will Darwin properly deal with modules that are both dynamically
linked against other modules and dynamically loaded?
For a high-level approach, see: <http://www.cocoadevcentral.com/
articles/000068.php>, for low level details, open your ADC Ref Lib
(Xcode -> Help -> Documentation), then select the Darwin -> Runtime
Architecture group (left pane). There's a document about dynamically
loading code.
The extension ".bundle" seems to be sticky in the Linux world, btw.
"Bundle" is the name for a collection of files with a known
hierarchy, nothing more. Typical examples are applications,
frameworks, plugins, ... rarely they are actually named ".bundle",
however.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/darwin-dev/email@hidden
