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: "Sean McBride" <email@hidden>
- Date: Mon, 3 Oct 2005 12:53:12 -0400
- Organization: Rogue Research
On 2005-09-30 16:33, Norm Schuster said:
>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.
Apple's choice allows non-bundled applications, like command line
utilities, to be fat also.
As for saving disk space, I'm sure we'll see a freeware that use lipo to
de-fat applications-- such a beast existed for the 68k/ppc case years ago.
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
_______________________________________________
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