Re: CPU archs for iOS apps?
Re: CPU archs for iOS apps?
- Subject: Re: CPU archs for iOS apps?
- From: Jeffrey Robert Kelley <email@hidden>
- Date: Fri, 16 Aug 2013 22:35:36 -0400
That second type is armv7s. The UIRequiredDeviceCapabilities key is a minimum. The CPUs in iOS devices can run older code, but not the other way around—so an armv7s CPU can run armv7 code, but an armv6 CPU cannot. By setting the key to armv7, you’re restricting it to CPUs that are capable of running armv7 code, which currently includes armv7 and armv7s chips.
As a side note, be sure you’re testing your app on a device that actually runs armv7s if you’re releasing it for that architecture. It’s extremely rare that there’ll be a bug on one but not the other, but I’ve never been comfortable shipping code I haven’t actually run.
On Aug 16, 2013, at 10:20 PM, Rick Mann < email@hidden> wrote: I noticed that my Info.plist specifies armv7 for UIRequiredDeviceCapabilities, but the binary built by the Archive command has two archs in it (and the plist only shows armv7):
Mach-O universal binary with 2 architectures
(for architecture armv7): Mach-O executable arm
(for architecture cputype (12) cpusubtype (11)): Mach-O executable arm
What's the right thing to be doing here?
--
Rick |
_______________________________________________
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