I have been reading the documentation of GCC to see the caveats of
this compiler and I really wanted to start using GCC 4.0 because it
makes smaller code at faster compiling speeds. However, the docs
state that we SHOULD NOT use GCC 4.0 if we want to deploy on
systems earlier than Mac OS X 10.3.9. It is not said we CANNOT,
only that we SHOULDN'T. My question is: why shouldn't we? What's
the penalty of that? Will an app break because of that? Or we will
find inexplicable runtime errors?
My understanding of it is that C++ projects built with GCC 4.0 will
not run on anything earlier than OS X 10.3.9 since they expect a
dynamic library to be present that wasn't bundled with the OS until
10.3.9. I don't remember the rules for non-C++ projects, but they're
a bit more relaxed.
Another question related to the first: is possible to compile my
code with GCC 4.0 to make sure that my code is cleaner and then
shift back to GCC 3.3 to assure compatibility with earlier Mac OS X
versions, or am I asking for trouble?
That sounds like a good idea to me. Each new release of GCC seems to
get stricter, so building with 4.0 will catch problems that 3.3
won't. I do this now as a consequence of having added Universal
targets to our projects. The regular targets still build with 3.3 so
they'll run on 10.2.8, but the Universal targets build with 4.0.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
