How to check if a static library is built for 64-bit?

ios objective-c static-libraries lipo
Joel Fischer picture Joel Fischer · Sep 25, 2013 · Viewed 48.6k times · Source

I just built a static library for iOS with the build setting for Architectures set to $(ARCHS_STANDARD_INCLUDING_64_BIT).

I want to make sure that the .a library is properly including that architecture, but when i run lipo -info on it, I see:

Architectures in the fat file: library.a are: armv7 armv7s (cputype (16777228) cpusubtype (0))

Does this mean that arm64 isn't included? If the lipo command can't tell me, is there another way to tell?

I'm running Xcode 5 with the latest Command Line Tools installed.

Answer

Stephen Canon picture Stephen Canon · Sep 25, 2013

Yes, an arm64 slice is there. To see it, you need to use lipo from the iOS toolchain, not from the host system (which doesn’t know about arm64):

xcrun -sdk iphoneos lipo -info $(FILENAME)

Related questions

File is universal (three slices), but it does not contain a(n) ARMv7-s slice error for static libraries on iOS, anyway to bypass?

I upgraded Xcode version and when using external static libraries, I get this message: ld: file is universal (3 slices) but does not contain a(n) armv7s slice: /file/location for architecture armv7s clang: error: linker command failed with …

Read More
Why linker link static libraries with errors? iOS

I have a problem with linking my mixed language framework to a project. 1) I create a framework with Swift and Objective-C classes. 2) The main logic was stored in the Swift file. For example the class with a method that calls …

Read More
Prevent duplicate symbols when building static library with Cocoapods

While I've seen many questions dealing with Cocoapods and static libraries, most of them seem to assume you'll eventually have a single workspace with your static library and end target app. In my scenario, I am building a static library. …

Read More