I’ve recently upgraded to 10.11 and Xcode 7. I have a MacOS app that I’ve been 
developing since 10.7 and the various versions of Xcode since. In prior 
versions of Xcode, I would set the base SDK to the latest and set the 
deployment target to 10.7, the minimum version my app supports. Now with Xcode 
7 under 10.11, it seems the base SDK is fixed at 10.11. Fine, as setting the 
deployment target to 10.7 should allow my app to build and then run on anything 
between 10.7 and 10.11. What I’ve found instead, is that while my app builds, 
it only runs properly on 10.10/11. In earlier versions of the OS, various 
portions of my program don’t work. 

My app uses Core Audio to enumerate and communicate with the audio devices 
connected to the computer. What I’m seeing on pre-10.10 versions of the OS is 
that some combination of the following issues are apparent: 

Devices are not enumerated
The interface is not updated when devices are connected/removed
AirPlay devices are not found. 

As you go down the OS versions, more of the issues appear, with 10.7 being the 
least functional of them all. I can build this code under older versions of 
Xcode and MacOS (I’ve built under 10.9 and 10.7, using Xcode 5, don’t have a 
copy of 10.8) and it runs just fine in the range of OS’s I need (10.7-10.11). 
I really can’t believe this is a code issue, if it is, I can ask on the Cocoa 
or Core Audio lists.


So my question to the group should be obvious:
Is there something I’m missing in my build configuration? Are there issues with 
Xcode 7 and deployment targets? 

In the meantime, I’ll set the deployment target to 10.8 and 10.9 and see if 
that makes a difference. I have tried that yet. Too busy googling and rebooting.

Thanks
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to