Re: Virtual Instances and XCode
Re: Virtual Instances and XCode
- Subject: Re: Virtual Instances and XCode
- From: Ken Thomases <email@hidden>
- Date: Thu, 26 Dec 2013 13:12:54 -0600
On Dec 26, 2013, at 12:03 PM, Patrick Cusack wrote:
> And that's why I ask as I have read different explanations. Some people say that you can build against the current SDK and target for the SDK of interest, but others say you must build against the actual SDK if you want to be certain.
It depends on what libraries or frameworks your project uses. Ones that originated from Apple should work with the deployment target. Ones that did not, such as open-source projects, won't. libcrypto has been a perennial problem in that respect. The Python framework is one that affects my work. If you link against those from the current SDK, then you have implicitly established a hard dependency on the current version of the OS and your binary won't load on earlier versions, regardless of how you've set the deployment target.
You also need to carefully read all of the release notes between your deployment target and your SDK. Often, when Apple fixes a bug, they keep the old behavior for apps linked against the old SDK and provide new behavior for apps linked against the new SDK. If you're going to be using the new SDK with an old deployment target, then you're going to get different behavior from the frameworks when your app runs on the newer OS than when it runs on the older. Your code may need to compensate. (Obviously, the new behavior is generally better. Sometimes you'll be able to write code one way to work fine with either behavior. But sometimes your code will need to behave differently to match the different behaviors of the frameworks.)
Regards,
Ken
_______________________________________________
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