site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Am 23.07.2005 um 03:57 schrieb Solra Bizna:

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.

Also, will Darwin properly deal with modules that are both dynamically linked against other modules and dynamically loaded? HTH, Markus - - - - - - - - - - - - - - - - - - - Dipl. Ing. Markus Hitter http://www.jump-ing.de/ _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl...

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.

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. This email sent to site_archiver@lists.apple.com