[
https://issues.apache.org/jira/browse/CB-5921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Graham Mueller updated CB-5921:
-------------------------------
Attachment: build
I'm attaching the build file that I've overridden to allow myself to build with
workspaces locally, which was requested by someone on StackOverflow. I don't
know that this is necessarily going to be useful when actually implementing the
feature, but it's a temporary workaround.
> Cordova on iOS should use an XCWorkspace, or at least support using one.
> ------------------------------------------------------------------------
>
> Key: CB-5921
> URL: https://issues.apache.org/jira/browse/CB-5921
> Project: Apache Cordova
> Issue Type: Improvement
> Components: iOS
> Reporter: Graham Mueller
> Priority: Minor
> Labels: core
> Attachments: build
>
>
> Hi Guys,
> Not sure what to log this as. It's not so much a bug as an incompatibility
> with other frameworks. Anyway, this is specifically an issue with the build
> process on iOS. Do with it what you will.
> If you're familiar with the CocoaPods framework, you'll know that on initial
> install, it creates an XCWorkspace file, and instructs you to exclusively use
> that afterwards. This is because the CocoaPods library adds itself as a
> linked project that must be built, similar to Cordova/Phonegap. The
> difference is that Cordova adds itself as a sub project, instead of a sibling
> project (which is effectively the workspace goal, from my understanding,
> though I'm having a hard time finding a good link to explain it better).
> So, I would suggest that Cordova moves to this setup as well -- it should
> create the workspace that has both the Cordova project and your app project.
> Alternatively, if you don't want to go through and change that creation code,
> it would be great if the CLI offered someway to specify what you want it to
> build. I found the actual build script that's calling xcodebuild with a
> -project flag in it (this is where -workspace would go). There is currently
> no way to override this, so there is currently no way at all to support
> workspaces (and consequently no way to use CocoaPods).
> Any thoughts or reasons not to do so?
> Thanks,
> Graham
--
This message was sent by Atlassian JIRA
(v6.2#6252)
