[
https://issues.apache.org/jira/browse/CB-11893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16356678#comment-16356678
]
Shazron Abdullah commented on CB-11893:
---------------------------------------
[~swinx] yeah we were going for one kind of scenario (the most general case,
with a restriction), but now as a workaround we should consider an "only
dynamic frameworks" scenario. So when one plugin uses it, we print out a
warning if other plugins that use CocoaPods don't use it. It will complicate
things however, detecting this scenario.
So, if your plugin uses a dynamic framework in a CocoaPod, you *must* specify a
flag. We can either overload the `type` or spec attribute. I prefer the `type`
attribute. Here's a `type` attribute example:
{code:java}
<framework src="MyPluginThatUsesADynamicFrameworkCocoaPod"
type="podspec:use_frameworks" spec="~> 1.2.0" />
{code}
I don't want to create another attribute since that requires changes in
cordova-lib, and not just cordova-ios. I'm just using the CocoaPods podfile
option name directly, instead of creating a new name (easy to remember)
> CocoaPods support: Provide a way to add use_frameworks! on the Podfile
> ----------------------------------------------------------------------
>
> Key: CB-11893
> URL: https://issues.apache.org/jira/browse/CB-11893
> Project: Apache Cordova
> Issue Type: New Feature
> Components: cordova-ios
> Reporter: jcesarmobile
> Priority: Major
> Labels: backlog
> Fix For: [email protected]
>
> Attachments: Integrating Static Library With Cocoapods
> Use_frameworks.pdf
>
>
> If the library you want to use on the plugin uses Swift or you want to use
> dynamic frameworks you have to add use_frameworks! on the Podfile
> I don't think there is a way of adding it right now.
> We should provide a way of adding it
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
