Let’s split package names by components: numpy — package name 1.13.3 — package version cp27 — the package was compiled to be used with this version of Python cp27mu — compilation flags linux — operating system armv7l — processor architecture This means that package numpy contains binary extensions written in C and compiled for specific … Read more
I ran into a similar problem myself. @graver‘s solution is definitely valid. The issue was that the library was being built for armv7 instead of armv7s. You can verify this yourself by using lipo <path/to/lib.a> -info. Setting the Build Active Architectures Only option to No fixes the issue. Hope this helps.
I’ve been able to do this successfully with my app that’s in the App Store. It supports armv6, armv7, and armv7s and iOS versions from 4.2 to 6.0. I’ve verified that it runs on older devices (iPhone 3G, iPod touch 2g) all the way through the iPhone 5. This method requires having both Xcode 4.5 … Read more
Sorry, but you aren’t right. The iPhone 3G and iPod Touch 2G are able to run iOS 4 (barely) and they include a armv6 processor. ARMv8 / ARM64 = iPhone 5s, iPad Air, Retina iPad Mini ARMv7s = iPhone 5, iPhone 5c, iPad 4 ARMv7 = iPhone 3GS, iPhone 4, iPhone 4S, iPod 3G/4G/5G, iPad, … Read more
The older iOS devices (iPhone, iPhone 3G, first and second generation iPod touch) had CPUs that only supported the armv6 instruction set. The iPhone 3G S (and iPad and third-generation iPod touch) has a newer processor that also supports the armv7 instruction set. In general, armv7 is faster on these newer processors and it is … Read more
Depends on what your native code does, but v7a has support for hardware floating point operations, which makes a huge difference. armeabi will work fine on all devices, but will be a lot slower, and won’t take advantage of newer devices’ CPU capabilities. Do take some benchmarks for your particular application, but removing the armeabi-v7a … Read more
If you don’t really need the mechanism, just specify a random flavor dimension in your build.gradle: android { … flavorDimensions “default” … } For more information, check the migration guide
Common Causes The common causes for “Undefined symbols for architecture armv7” are: You import a header and do not link against the correct library. This is common, especially for headers for libraries like QuartzCore since it is not included in projects by default. To resolve: Add the correct libraries in the Link Binary With Libraries … Read more