[
https://issues.apache.org/jira/browse/CB-5921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389851#comment-14389851
]
Carlos Santana commented on CB-5921:
------------------------------------
[~shazron] This is great here in IBM we are looking at Cocoapods as the defacto
standard for building libraries for developers to include the IBM SDKs. I know
you already mentioned that we don't allow external packages dictate where
Cordova should go, but this is building block if we want to use cocoapods to
take what cordova produces (core and plugins) then produce cocoapods that are
portable int he cocoapods ecosystem.
cocoapods is something we can leverage little or more as cordova see it fit, I
think there are things that the pod client handles well that we don't have to
re-invent the well like editing xcbuild files to add or remove pods/frameworks
I will check your branch out and make comments in gihub, I'm curios to see how
you are packaging the web parts of the plugin as resources bundle, and then
make it available to the web view, it was the only part I didn't have a clear
picture how to solved.
> 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
> Fix For: 4.0.0
>
> 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.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
