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

Shazron Abdullah commented on CB-5921:
--------------------------------------

Plugin adding can be solved by making each plugin into a Static Library project.
1. Create a static library project ($pluginname) with the plugin files added 
(with appropriate build phase settings)
2. Add the static library to the $projectname.xcworkspace (xml)
3. For the $projectname Build Phase -> Link Binary with Libraries, add the 
lib$pluginname.a library to the project

However, the static library approach will not take into account resource 
bundles in the plugins. In iOS 8, we can use .frameworks, but we still need to 
support iOS 7 however (not sure about backwards compat. if we use iOS 8 
frameworks).




> 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

Reply via email to