[
https://issues.apache.org/jira/browse/CB-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13467063#comment-13467063
]
Andrew Grieve commented on CB-1526:
-----------------------------------
Good point. I've now deleted CordovaBuildSettings.xcconfig from the project
template.
After a good amount of discussion, we're going to move towards a model where
the project template includes a copy of CordovaLib, so that checking CordovaLib
into source control will not be an additional step.
> Putting CordovaLib in source control requires bin/update_cordova_subproject
> ---------------------------------------------------------------------------
>
> Key: CB-1526
> URL: https://issues.apache.org/jira/browse/CB-1526
> Project: Apache Cordova
> Issue Type: Wish
> Components: iOS
> Affects Versions: 2.1.0
> Reporter: Jacob Weber
> Assignee: Andrew Grieve
> Priority: Minor
>
> As of version 2.1, the path to the CordovaLib subproject is now hard-coded as
> a relative path from your Xcode project, instead of being defined by a
> CORDOVALIB variable.
> If you're putting your project in version control, this means you now need to
> include CordovaLib in your project, so the relative path will work for other
> developers.
> After you copy it into version control, you need to run
> bin/update_cordova_subproject to set the path in your Xcode project.
> But this script always looks for CordovaLib in its parent directory. This
> means that you need to temporarily copy bin/update_cordova_subproject into
> your own project, run it, then remove it.
> It would be better if we could pass update_cordova_subproject the path to the
> CordovaLib we want to use.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira