Xcode armv6 armv7 armv7s arm64

There are currently several instruction sets for iOS:

• ARMv6
  • Iphone
  • IPhone2
  • Iphone3g
  • First generation and second generation ipod Touch
• ARMv7
  • IPhone4
  • Iphone4s
• armv7s
  • IPhone5
  • iphone5c
• Arm64
  • IPhone5S

The machine's support for the instruction set is backwards compatible, so the armv7 instruction set can be run in iphone5s, but not as efficient as it is.

================================================

Architecture: Refers to the set of instructions you want to support.

Valid architectures: Refers to the set of instructions that will be compiled.

Build Active Architecture only: Compiles only the currently applicable instruction set.

================================================

This is the beginning of 2014, in fact, 4 and 4S users are quite a lot, and iphone3 and other machines almost no, so our instruction set minimum must be based on ARMV7.

Therefore, the value of architecture is selected: ARMv7 armv7s arm64

PS: Minimum support required when selecting Arm64 5.1.1:

Convert Your App to a 64-bit Binary after Updating It for IOS 7

Xcode 5.0.1 can build your app with both 32-bit and 64-bit binaries included. This combined binary requires a minimum deployment target of IOS 5.1.1 or later. The 64-bit binary runs only on 64-bit devices running IOS 7.0.3 and later. If you have a existing app, you should first update your app for IOS 7 and then port it to run on 64-bit processors. By updating it first for IOS 7, you can remove deprecated code paths and use modern practices. If you ' re creating a new app, target IOS 7 and compile 32-bit and 64-bit versions of your app.

The architecture for 64-bit apps on IOS are almost identical to the architecture for OS X apps, making it easy to create a Common code base that runs in both operating systems. Converting a Cocoa Touch app to 64-bit follows a similar transition process as the one for Cocoa apps on OS X. Pointers an D Some common C types change from + bits to + bits. Code that relies on the NSInteger and CGFloat types needs to be carefully examined.

Start by building the app for the 64-bit runtime, fixing to warnings that occur as well as searching your code for SPECIF IC 64-bit issues. For example:

• Make sure all function calls has a proper prototype.

• Avoid truncating 64-bit values by accidentally assigning them to a 32-bit data type.

• Ensure that calculations is performed correctly in the 64-bit version of the Your app.

• Create data structures whose layouts is identical in the 32-bit and 64-bit versions of your apps (such as when you write a Data file to ICloud).

1, if you want your app to be able to run most efficiently on each machine, you need to change build Active Architecture only to No,valid architectures select the corresponding instruction set: ARMv7 armv7s arm64. This will compile the corresponding code for each instruction set, so the final IPA volume is roughly 3 times times, and the release version must be No.

2, if you want to keep the app volume is minimal, then the current stage should choose valid architectures as ARMV7, so build Active Architecture only Select Yes or no does not matter

Common commands:

1. The command to view the support framework is Lipo-info XXXXX.A
2. The command to merge the libraries of the real machine and simulator is lipo-create XXXX_IPHONEOS.A xxxx_simulator.a-output xxxx.a

Xcode armv6 armv7 armv7s arm64