[ 
https://issues.apache.org/jira/browse/CB-6716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14550992#comment-14550992
 ] 

Christopher Johnson commented on CB-6716:
-----------------------------------------

[~shazron]

This issue is still very relevant to my clients and was not resolved with 
#6728.  In my case we are automating IOS builds with a build server using the 
cordova command line tools.  I'm starting to run into multiple 3rd party 
cordova plugins with library dependencies built without armv7s support.  Since 
cordova includes armv7s in the valid architectures list my builds cannot 
succeed.

> XCode 5.1 Valid Architectures ignored/misread by Cordova CLI 3.4.1?
> -------------------------------------------------------------------
>
>                 Key: CB-6716
>                 URL: https://issues.apache.org/jira/browse/CB-6716
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: CLI
>            Reporter: Peter O'Shaughnessy
>            Priority: Minor
>
> cordova 3.4.1-0.1.0
> XCode 5.1 (5B130a)
> iOS 7.1
> I am new to Cordova (and this issue tracker) so apologies if this is just my 
> misunderstanding. But the CLI doesn't seem to be picking up the iOS 'Valid 
> Architectures' configuration?
> In XCode, I have specified Valid Architectures as only "armv7s armv7". 
> (Because I'm using a framework that doesn't work with arm64).
> But {{cordova build --device ios}} and {{cordova run --device ios}} report 
> VALID_ARCHS as "armv7 armv7s arm64". And then it fails with "{{symbol(s) not 
> found for architecture arm64}}".
> I can skirt around the issue by changing "Build Active Architecture Only" to 
> "Yes". Or by building and running through XCode. But it would be good to know 
> why there's this discrepancy with the command line?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to