armv6

I have an XCode project configured like this: Project Format: XCode 3.1-compatible Architectures : Standard (armv6 armv7) Base SDK : Latest iOS (currently set to iOS 4.2) Build Active Architecture Only : UNCHECKED Valid Architecures: armv6 armv7 My question: Does the resulting binary (.ipa) have 2 executables in it - one for each architecture, or just some different object files for each architecture or is the split even finer grained than that? Just curious. Thanks. McCygnus From what you described, the ipa should have a multi-architecture binary with both arm6 and arm7. You can check it with

Starting with Xcode 4.5 the possibility of building for armv6 devices is not given anymore (iPhone/iPod touch 1st and 2nd generation). This means no new versions of our app for iPhone 2G and 3G which is very unlucky. Does anyone know if there will be a workaround? I really don´t see any technical reasons for this. You can have multiple versions of xcode installed. In the past, that has been the fix needing to use an older xcode feature. It is a workaround, and the project files may eventually evolve in a way that no longer supports the older tools, but for the time being, that will allow you

Trying to compile a basic program which uses pcap.h. I've set up the environment on my Mac OSX box which uses the iPhone 3.1.3 SDK for an iPhone 3GS. I've also installed libpcap to ~/libpcap so I can tell gcc where to look for the headers using the -I flag. However, it fails with an ld warning saying the file is not of the required architecture. I'm compiling with the following line: /Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/gcc -I /Users/abnev/libpcap/include -arch armv6 -isysroot /Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS3.1.3.sdk -o pcap pcap.c -lpcap

In compiling iPhone apps, there is a setting for "Optimized" architecture (armv7 only) vs a standard armv6/armv7 architecture. What are the benefits/consequences of compiling an armv7 only architecture? A smaller executable is a faster download from the app store. However, you do cut out non-armv7 devices . Unless your program requires OpenGLES 2.0 (which is only supported on armv7-supporting devices), you should compile the standard fat (armv6/armv7) binary. A fat binary is basically two (or more) Mach-O binaries glued together, with a single header page at the beginning. The performance cost

I'm trying to run an app on a 3G device. Xcode says that the app has "Finished running on the iPhone" but the app will not deploy. I think I have the architectures configured correctly (see image below) any help would be great, thanks I figured this out finally. In the Info.plist there's a "Required device capabilities" setting that was set to armv7. I was aware of the armv6 and armv7 requirements in the target build settings for the 3G model but not in the plist. here's a screenshot. hope it helps anyone else stuck with something similar: Your configuration looks fine. I’ve seen this before;

Crash log contains "Binary Images" section with information about architecture (armv6/armv7) and identifier of all loaded modules. How to determine this information at runtime? (at least, just for application executable) NSBundle has method executableArchitectures, but how to determine which architecture is running? Alright time for the long answer. The mach headers of the dyld images in the application contain the information you are looking for. I have added an example that I only tested to work and nothing else so I would not recommend pasting it directly into production code. What it does

I have a 3rd party .a library, which is apparently compiled for only armv6 compatibility, where both new Xcodes (3.2.6 and 4), both now require a separate armv7 slice to run on the device. The link error is: file is universal but does not contain a(n) armv7 slice for architecture armv7. Anyone know how to make either of the two new Xcode operate as 3.2.5 did and accept the existing library while I'm waiting for the library vendor to cook up an armv7 version? In Project Settings, select "Standard" for the architecture (not "Optimized"). This should allow you to select "armv6" for the Active

I have two 3rd party libraries. One just has a build for armv6 and the other just has a build for armv7. I need to use both of them in my iOS enterprise application. I've asked the armv6 library vendors to supply a armv7 version, but they haven't been able to do so. (Note: I've already got the answer and will provide it. Someone else asked this in a comment and there wasn't enough room to answer, so I've created its own question, and will provide my answer.) The answer is to hack the armv6 library into thinking it's an armv7 library. This will get you running until the vendor supplies the