On Jul 21, 2011, at 15:58, Fritz Anderson wrote: On 21 Jul 2011, at 7:18 AM, Christiaan Hofman wrote: I'd like to know what is the easiest way to keep my Xcode 3.2.6 when upgrading my computer for Lion. Does the Lion installation leave the developer folder in place, or should I first move it away to keep it, perhaps archived?
If I were you, I'd rename the old /Developer folder. I don't know whether the official-release installer lets you choose and name the folder that receives Xcode 4.1.
In fact, I'd be very grateful if someone would tell me.
People with legacy projects depend on it.
Also (some) developers, like me, who want their apps to be backward compatible to 10.5 or earlier.
Apple repeatedly says that applications compiled against the 10.6 or 10.7 SDKs are backward-compatible to any earlier Mac OS X, so long as you stick to the earlier API. This is true, as far as it goes.
When it's about API, that's generally true. But when it's about linking to libraries, it's often not true. For instance libcrypto has compatibility version 0.9.8 in the 10.6 SDK, but 10.5 has version 0.9.7, so it will fail to link there. What's worse, the compiler won't warn you about this. And Apple has consistently ignored, and repeated, these problems (so I don't care what Apple says when I know it's a lie...).
However, it was always a useful trick to set the active SDK to an earlier version for a build or two, so you could be sure you weren't relying on API that wasn't available in the latest SDK.
I agree with that, and also do that routinely. In fact, because of the problems I noted, I am still forced to use the 10.5 SDK today, that's also why I really need 2.3.6.
And Apple not only doesn't acknowledge this, they keep saying that you should ALWAYS use the latest SDK. Tell me again why I should listen to them? Apple people, at least publicly and on this list, have been so pointedly obtuse on the question that I wonder if they haven't been instructed not to acknowledge it. One could speculate (and it would be only speculation) on why that is.
— F
It's easier to deny a problem than work hard to fix it, I guess, especially if it's not you who has the problem. Seriously, that's the only explanation I can think of.
Oh, and as it's possible to use 2.3.6 on Lion, can it also be used to build a PPC binary, and has anyone tried that?
Christiaan
|