On 22 Jun 2015, at 10:32 am, Quincey Morris <[email protected]<mailto:[email protected]>> wrote:
On Jun 21, 2015, at 16:07 , Nick Blievers <[email protected]<mailto:[email protected]>> wrote: To avoid this you need to use something like NSClassFromString, so that all references to the object are dynamic. I think this is not the complete story. Automatic weak linking of frameworks works for OS X now, and my vague recollection is that it was introduced mid-major-version of OS X, perhaps at 10.6.8. (Again I don’t recall, but it may have only been introduced for the new non-fragile ABI, which is probably why the 32-bit version has different behavior.) Therefore, it’s possible that setting the deployment target to 10.6.8 will resolve the issue, assuming Xcode knows what it’s doing. (Of course, that cuts the app off from earlier 10.6 users, but so much changed and got fixed at 10.6.8, that these users really ought to have upgraded.) Alternatively, manually forcing the framework to be weak-linked might allow the current code to work back to 10.6.0. Hmm, I completely forgot about that and just defaulted to the manual way of doing things. You are right, automatic weak linking should cover it. I’ll stfu now :) Nick
_______________________________________________ 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]
