Re: Xcode 3.2.6 on Lion ?
Re: Xcode 3.2.6 on Lion ?
- Subject: Re: Xcode 3.2.6 on Lion ?
- From: Simon Wilson <email@hidden>
- Date: Fri, 22 Jul 2011 10:12:53 +0200
> Apple repeatedly says that applications compiled against the 10.6 or 10.7 SDKs are backward-compatible to any earlier Mac OS X
This is not necessarily the case.
For example, applications linking against OpenSSL in the 10.6 SDK will not run on 10.5. Also, the behavior of certain classes in AppKit also subtly changes when linked against the 10.6 SDK.
If you want to be able to reliably build on 10.6 and distribute to 10.5, 10.6 (and probably 10.7) with the same behavior on all platforms then building against the 10.5 SDK is your only option.
Xcode 4.1's lack of support for the 10.5 SDK mean that you will most probably need to keep 3.2.6 around on Lion. This is OK if you're upgrading from Snow Leopard (just install Xcode 3 first), but this is a non-starter for developers purchasing new Macs with Lion pre-installed.
Running Snow Leopard in a VM with Xcode 3 might be the answer, but you'll need 10.6 Server as the desktop edition license agreement doesn't permit virtualization.
Failing that you'll have to either stay on 10.6 or keep a second Mac around with 10.6 Xcode 3.
Apple has made this difficult enough that I suspect most developers will quickly drop support for 10.5 now that Lion is out. This is certainly what we'll be doing.
Cheers,
Simon
On 21 Jul 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.
>
> 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. 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
>
> _______________________________________________
> 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
_______________________________________________
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