Re: Why does Xcode claim a lib has no ARMv7 "slice", when lipo shows that it's all ARMv7?
Re: Why does Xcode claim a lib has no ARMv7 "slice", when lipo shows that it's all ARMv7?
- Subject: Re: Why does Xcode claim a lib has no ARMv7 "slice", when lipo shows that it's all ARMv7?
- From: Roland King <email@hidden>
- Date: Tue, 25 Sep 2012 18:30:32 +0800
Sorry I was going to type more but sent by mistake and figured you'd probably sort it out.
armv7s is what the iPhone 5 uses. I'm assuming at some point you switched to Xcode 4.5 and the latest SDK so the standard compile includes armv7 and armv7s, so you need a library with both.
You can change the build script of the static library so it does both, or it is possible to just remove armv7s from your actual final target build and just build for armv7, just means that certain operations won't take full advantage of the iPhone 5 hardware, whilst you get it figured out. AFAIK apps can be submitted like this too, but it's something I would strive for. This is all in the build settings. I would have thought just changing the static library build script to have the two architectures in the same format the final target build has them would 'just work' and build a 2 architecture static library.
On 25 Sep, 2012, at 6:21 PM, Gavin Stokes <email@hidden> wrote:
>> armv7s
>>
>>
>> note the s on the end.
>
> Thanks. What is armv7s, and how does one compile for it? A quick
> search didn't reveal any obvious references to it online. I'm using a
> build script for OpenSSL that configures the build for armv7.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden