Re: app built on 10.9 refuses to launch on 10.7
Re: app built on 10.9 refuses to launch on 10.7
- Subject: Re: app built on 10.9 refuses to launch on 10.7
- From: Scott Ribe <email@hidden>
- Date: Thu, 29 May 2014 20:44:31 -0600
On May 29, 2014, at 8:21 PM, Alex Hall <email@hidden> wrote:
> ...double clicked the .app file… and nothing at all happened. No errors, no blank windows, it simply didn't open at all.
Typical cause for this is trying to link to a dynamic library that is not found. Check console.app, there will be an entry if this is the case. Also, IIRC, there will be a crash report even though you didn't see a dialog informing you of the crash.
> Weak linking seems to be frowned on by users...
??? Users have no f'ing idea what weak-linking is. But unless you want to use post-10.7 features on post-10.7 Macs, it's not what you need anyway. Weak linking is only the solution to the problem of how to use different features on different OS versions, not the solution to how to implement a single set of code/features that runs across multiple versions.
Also, I don't understand why you can set a deployment target of 10.7 but cannot set an SDK of 10.7. Perhaps someone else can help, but I thought that if you managed to get the 10.7 SDK installed in the right place, that you could set both to 10.7 What version of Xcode are you using? I'm still on 5.0, and I have both deployment target and SDK set to 10.7, after copying in the 10.7 SDK from an older version.
--
Scott Ribe
email@hidden
http://www.elevated-dev.com/
(303) 722-0567 voice
_______________________________________________
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