On Jan 24, 2013, at 4:08 PM, Jeffrey Walton <email@hidden> wrote:
> Thanks David,
> So I'm clear, there is no way to tell `ld` that "its OK to use ARMv7
> since the A6 processor is backwards compatible." (I'm looking through
> ld's man pages now).
I'm not aware of any way offhand. Maybe someone else might know, but I don't.
>> Don't modify Valid Architectures, modify Architectures instead (you can specify to build only armv7 yourself).
> I seem to recall problems when I tried that (I'm likely wrong since
> you are rarely wrong).
> To be clear, I will delete $(ARCHS_STANDARD_32_BIT), and then add
> armv7. The ARMv7 code will then run on iPhone 5 and iPad 4 (A6
> processors, ARMv7s instruction set).
Yes, that should do it.
>> Until you can rebuild your library for armv7s, just build your main application for armv7 only.
> That's probably going to be distant future. Its easy to build the
> library from ARMv7s. Technical feasibility is not the problem.
> NIST and the Testing Lab can be political problem (believe it or not).
> Unfortunately, no one knows what NIST's position is, and the Testing
> Lab has not interpreted the NIST gospel or taken a position.
> If we final link OpenSSL (ARMv7) to an App (ARMv7s), then A6
> processors basically becomes a 'compatible platform'. So we can side
> step the entire minefield.
> Thanks again,
> On Thu, Jan 24, 2013 at 6:50 PM, David Duncan <email@hidden> wrote:
>> On Jan 24, 2013, at 2:55 PM, Jeffrey Walton <email@hidden> wrote:
>>> I know I can resolve this by removing ARMv7s from Valid Architectures (VALID_ARCHS).
>> Don't modify Valid Architectures, modify Architectures instead (you can specify to build only armv7 yourself). Until you can rebuild your library for armv7s, just build your main application for armv7 only.
>>> Or I can perform an additional build of the library for the ARMv7s architecture, but that's more work and requires a different on-disk directory structure.
>> I'm uncertain what would need to change here to be honest, as I would expect your build process to generate a single output binary that contains both the armv7 and armv7s code...
>>> Plus, ARMv7s could raise procedural questions with NIST and the testing Lab.
>> Assuming your main binary goes through the same testing procedures as your static library, you are already in this case since the main binary will need to be tested on armv7 and armv7s devices.
>>> Is there any magic to link an ARMv7 library with an ARMv7s application?
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden