> On May 14, 2015, at 12:05 PM, Chris Hanson <[email protected]> wrote: > > This is not supported; the Mach-O format doesn't have a way to distinguish > between targeted platforms, so you can't mix platforms in a single file. And > iOS Simulator is a separate platform from iOS (and OS X).
I understand that it isn’t supported, but as long as it works in practice, and Apple continues not to provide any better approach, I’ll keep using it. By “better” I mean “easier to configure, with fewer moving parts”. Your suggestion about FRAMEWORK_SEARCH_PATHS is a good one, and better than the mess I was dealing with for dynamic frameworks, but I still don’t relish having to explain this to developers. I know from experience that the more steps there are to using our library in an app, the more developers will get it wrong and come to us for help (or worse, just give up.) Ideally it should just be “download the framework and drag it into your Xcode project,” and for our cobbled-together fat static framework it’s pretty close to that easy. —Jens
_______________________________________________ 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]
