>> My question now is: why did Xcode not warn me about that function, even >> though the deployment target was set to 10.12 ? > The deployment target not a compiler setting. It is more of a runtime > thing. So if you set the deployment target to 13.0 it will not launch on > macOS 12, for
Oh, I see. That explains a lot. > example. The SDK is what determines what API are (not) available. So if you > were building against the 10.12 SDK you would have gotten a compiler error. Sorry for asking (again?): how would I do that? How do I install old SDK's on current Xcode / macOS? How would I tell Xcode to use those old SDK's? Is there an easy switch back and forth? Best regards, Gabriel
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
