4 ms·
Pretty sure it has zero to do with 64-bit processors. iOS7 is still going to be running on old 32-bit chips.
by untog 13y ago
Pretty sure it has zero to do with 64-bit processors. iOS7 is still going to be running on old 32-bit chips.
- pdpi 13y agoYes, which is precisely why you need 64-bit/32-bit fat binaries. Problem is that the current SDK can only generate 64-bit/32-bit fat binaries for iOS7 alone.
- mikeash 13y agoYou don't "need" fat binaries. You can just build for 32-bit and be happy. 64-bit is purely optional.
- untog 13y agoYes, which is precisely why you need 64-bit/32-bit fat binaries. I don't recall OSX refusing to run 32-bit binaries when it allowed 64bit computing.
- pdpi 13y agoYou don't need the fat binary to make 32-bit work in 64-bit machines. You need it to make it so that you can take advantage of the 64-bit machine with a build that still works in a 32-bit machine.
- ianstallings 13y agoAlthough you can do both, either 32-bit only or a combined, the preferred way to do it is as you say, a combined binary. I imagine that the differences will be fairly small because of the shared types and the resource sizes not changing. I'll have to experiment and see the results. Just a note on how to build for 32 bit and still target IOS: You have to set the architecture for armv7, armv7s and then set your deployment target to 7. I have yet to deploy an app doing this so your mileage may vary.