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

Shazron Abdullah commented on CB-1223:
--------------------------------------

This below does not work, but adding here as part of the research.

You can pass in an -xcconfig parameter to xcodebuild. So you would think you 
can set the CORDOVALIB variable in a temp file that has this, but no.

You can test this out by running:
{code}
xcodebuild -xcconfig [TEMP_CONFIG_FILE] -list [PROJECT_NAME].xcodeproj
{code}

It will not list the CordovaLib target, which is needed. It seems that 
xcodebuild loads up the Source Trees settings from 
~/Library/Preferences/com.apple.dt.Xcode.plist and linked project .xcconfigs 
ONLY and ignores any command line settings after (Xcode bug? I wouldn't be 
surprised). The previous comment above is the only known workaround for now.
                
> CORDOVALIB Xcode variable - allow this to be read in from xcodebuild cli
> ------------------------------------------------------------------------
>
>                 Key: CB-1223
>                 URL: https://issues.apache.org/jira/browse/CB-1223
>             Project: Apache Cordova
>          Issue Type: Task
>          Components: iOS
>    Affects Versions: Master
>            Reporter: Shazron Abdullah
>            Assignee: Shazron Abdullah
>             Fix For: 2.1.0
>
>
> Currently if you pass in a CORDOVALIB variable to xcodebuild it is ignored, 
> it still tries to read from the Xcode preferences plist com.apple.dt.Xcode 
> and/or the .xcconfig
> This is important for environments (CI) that have multiple versions of 
> Cordova installed and switch between them through the command-line

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to