Re: loading executable code, NSBundle
Re: loading executable code, NSBundle
- Subject: Re: loading executable code, NSBundle
- From: Andreas Wolf <email@hidden>
- Date: Wed, 2 May 2001 13:32:00 -0700
Thank you, Douglas!
I'd like to learn more about that, what would be a good reference for
that?
Is it kernel specific, OS X specific or cocoa? Sounds like deep down in
the kernel..
-Andreas
The behavior you see here is that of Mach-o binaries. There are many
different types of Mach-o binaries, but the three you will see most
often are stand-alone executables, dynamic shared libraries, and
loadable bundles. These three all have different behaviors:
stand-alone executables can be executed but not loaded; dynamic shared
libraries can be loaded, but not unloaded or executed; bundles can be
loaded and unloaded, but not executed. There are also a number of
other subtler differences. Your application bundle had a Mach-o
stand-alone executable as its binary, so it could not be loaded. When
you changed it to a bundle, it was compiled to have a Mach-o loadable
bundle as its binary, so it could then be loaded.
Douglas Davidson