On May 17, 2011, at 11:25 PM, Quincey Morris wrote: On May 17, 2011, at 18:31, Howard Rodstein wrote: However, on May 13, 2010, Chris Espinosa wrote on the Xcode mailing list: "Running on 10.4 requires gcc 3.3 or 4.0. gcc 4.2 does not generate code
that runs on 10.4."
and Xcode 4 does not include GCC 4.0.
-- I don't *know* anything useful about gcc 4.2 code generation vs. 10.4 deployment targets, but my *guess* is that it compiles for the Obj-C 2.0 runtime only, which AFAIK isn't present on 10.4, so avoiding post-10.4 API won't help, and even avoiding 2.0 runtime features at the source code level may not help. (It's possible that this entire statement is false, since I'm speaking out of a combination of memory and guesswork.) I wouldn't assume that a test with a simple plugin is going to give you reliable results. You may have simply failed so far to find the incompatibilities, and it sounds like you wouldn't want your users to have to find them for you.
If it is the case that running on 10.4 requires gcc 3.3 or 4.0, neither of which is included with Xcode 4, then why is "Mac OS X 10.4" an available option in the Mac OS X Deployment Target menu in the Build Settings?
Trying to clarify if this inconsistency is an oversight in the Xcode 4 build settings UI, a mistake in the understanding of the statements quoted in this thread, or possibly has some other use (where selecting 10.4 as the deployment target in Xcode 4 would be useful) which I am overlooking.
|