Re: ENABLE_BITCODE=NO and assistive applications
Re: ENABLE_BITCODE=NO and assistive applications
- Subject: Re: ENABLE_BITCODE=NO and assistive applications
- From: Jens Alfke <email@hidden>
- Date: Wed, 16 Sep 2015 09:35:57 -0700
> On Sep 16, 2015, at 4:24 AM, Bill Cheeseman <email@hidden> wrote:
>
> So, Chris, I'm very surprised at your assertion. Like many OS X developers, I don't have time to watch all of the WWDC videos. But I do spend substantial time every day reading the Apple tech news, and I like to think I'm keeping up to date. I especially rely on key documents like the Release Notes to tell me things I need to know.
I agree with you in general that Apple’s documentation can be pretty shoddy and often leaves out important details, or hides them in obscure places you can’t find easily (because the search engine in Xcode’s doc viewer is terrible.)
However, having worked on compiling release notes for various things over the years, I don’t recommend relying on release notes to tell you everything about a new version of a product. Release notes are to tell you about the existence of changes, not to describe the changes in full detail*.
I decided to search for “bitcode” in the doc viewer in Xcode 7, to see what I could find.
The top hit is “Uploading your app to iTunes Connect” (which I can’t link to because the doc viewer sucks.)
Searching for “bitcode” on that page, I find:
> To include bitcode, ensure that “Include bitcode” is checked (bitcode is enabled by default).
> Apps you upload to iTunes Connect that contain bitcode will be compiled and linked on the App Store. Including bitcode allows the App Store to apply updates to your app without requiring you to create a new version and resubmit it to App Review.
> • For iOS apps, bitcode is optional.
> • For watchOS apps, bitcode is required. If you uncheck this box, only the bitcode for the enclosed iOS app is removed.
> • For Mac apps, bitcode is not supported and this checkbox doesn’t appear.
So this is documented and not hard to find.
(It also makes sense if you think about it, because the purpose of submitting bitcode is to make it easy for the app to run on new CPU architectures without you having to rebuild it yourself; and new CPU architectures are very likely for iOS and watchOS because Apple designs and builds those CPUs, but not likely for Macs because they use totally standard Intel x86 silicon.)
—Jens
* except that, fairly consistently, there are important/useful tidbits of info about new OS releases that are _only_ mentioned in places like the Foundation/AppKit release notes, not in any ‘real’ docs. Sigh.
_______________________________________________
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