Universal binaries and older versions of Mac OS X
Universal binaries and older versions of Mac OS X
- Subject: Universal binaries and older versions of Mac OS X
- From: Greg Hurrell <email@hidden>
- Date: Tue, 7 Jun 2005 14:54:18 +0200
I've downloaded Xcode 2.1 and read the Universal Binary Programming
Guidelines[*] and my reading tends to indicate that to build a
Universal Binary you need to set your "Mac OS X Deployment Target" to
10.4 or later.
The question is, then, what is Apple's recommended best practice for
developers who maintain apps which must also run on older versions of
Mac OS X?
For example, imagine a product that currently runs on Mac OS X 10.2
and up (PowerPC). In the future one would like it to run on Mac OS X
10.2 and up (PowerPC) and Mac OS X 10.4 and up (Intel). There are
three possible solutions:
1. Make a Universal Binary (but the docs suggest this isn't possible).
2. Maintain two separate builds: a non-universal one for pre-Tiger
versions of Mac OS X and a universal one for Tiger and up.
3. Abandon support for pre-Tiger versions of Mac OS X and force your
customers to upgrade.
4. Forget native code and rely on "Rosetta".
Obviously "1" would be the most elegant option, "2" would be a pain,
"3" would alienate some customers, and "4" would involve a
performance hit and in some cases not work at all due to limitations
in Rosetta.
So what are Apple's recommendations in this kind of case?
Cheers,
Greg
*http://developer.apple.com/documentation/MacOSX/Conceptual/
universal_binary/universal_binary.pdf
_______________________________________________
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