Re: Xcode 9 - no more Mac development?
Re: Xcode 9 - no more Mac development?
- Subject: Re: Xcode 9 - no more Mac development?
- From: Quincey Morris <email@hidden>
- Date: Wed, 21 Jun 2017 23:55:41 -0700
On Jun 21, 2017, at 23:43 , Jack Brindle <email@hidden> wrote:
>
> While playing with the Xcode app this evening
> I copied the 10.12 SDK into it.
Well, I hate to be Bad Cop, but don’t do that. It’s never, ever been supported
to copy older SDKs into newer Xcodes, and while you *might* get away with it in
Obj-C, you’re probably going to crash and burn in Swift (because the API
migrator may have dependencies on annotations in the later SDK).
It also isn’t necessary any more. In the past, the reason for using an old
SDK** was to use the version of the SDK that matched your deployment target, so
that you couldn't accidentally use new APIs that would crash on older Macs.
Starting in Xcode 9, Obj-C has finally (finally!) added the ability to warn you
if you use newer API not supported on the deployment target, if you don’t do it
conditionally on a version check. So, you really *should* be using the 10.13
SDK regardless of deployment target.
Given that we’ve been begging Apple to do this for Obj-C for 10 years or more,
it seems churlish not to take advantage of it.
** The only remaining case where you might want to use an old SDK is when your
(old) app depends on a behavior that is in turn dependent on which SDK it was
linked with. But you’re better off fixing and/or conditionalizing such
scenarios.
_______________________________________________
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