Re: How do I build universal binaries for libraries with endian-specific code
Re: How do I build universal binaries for libraries with endian-specific code
- Subject: Re: How do I build universal binaries for libraries with endian-specific code
- From: Damien Bobillot <email@hidden>
- Date: Mon, 3 Oct 2005 00:21:20 +0200
Norm Schuster wrote : Also, why didn't Apple just add another folder in the bundle containing two different executable files like it did with PEF and Mach-)? Why not have a bundle structure like this:
/Contents/MacOSClassic/PEF_Executable_PPC
/Contents/MacOS/MachO_Exectuable_PPC
/Contents/MacOSIntel/MachO_Executable_Intel
This would have made more sense rather than having a "fat" application with no obvious way to make it leaner. The Contents/SomeThing/... is used for different systems (and different executable formats), not for different architectures. One may imagine a Contents/Linux/ or a Contents/Windows/ for multiplatform applications (each version may even use totally different APIs).
The fat object format is used to stored many code variants (PPC/x86, but also G3/G4/G5 or a potential intel/AMD variants). In this case, the variant use the same executable format, and the same APIs.
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden