iOS: Cordova framework target

[Kevin Hawkins <ke...@gmail.com>]

I've been long out of the day-to-day happenings of the Cordova project, so
I apologize if this ground has been covered before; I searched back through
my archive and didn't immediately see anything related.  I'll see if I can
keep this description as concise as possible.

For our iOS SDK, we ship a dynamic framework that depends on Cordova.  We
have consumers who depend on both our framework and directly upon Cordova.
They would like to be able to manage their Cordova dependency themselves.
The cleanest way to do this would be if we could both build a
"Cordova.framework" out of the CordovaLib project, and manage the Cordova
dependency itself as a dynamic framework.

I know this isn't the way most people consume Cordova—the approach is more
of a traditional native iOS app with hybrid dependencies.  But it also
doesn't seem like a huge stretch to provide the additional target in the
CordovaLib project.  It's something we could probably take a look at
contributing, but I wanted to float the idea to the list first, to get a
sense of any reservations.

Thanks!
Kevin

Re: iOS: Cordova framework target

[Kevin Hawkins <ke...@gmail.com>]

I guess CB-12050 <https://issues.apache.org/jira/browse/CB-12050> would be
related, as far as that goes.

On Tue, Jan 17, 2017 at 3:13 PM, Kevin Hawkins <
kevin.hawkins.cordova@gmail.com> wrote:

> I've been long out of the day-to-day happenings of the Cordova project, so
> I apologize if this ground has been covered before; I searched back through
> my archive and didn't immediately see anything related.  I'll see if I can
> keep this description as concise as possible.
>
> For our iOS SDK, we ship a dynamic framework that depends on Cordova.  We
> have consumers who depend on both our framework and directly upon Cordova.
> They would like to be able to manage their Cordova dependency themselves.
> The cleanest way to do this would be if we could both build a
> "Cordova.framework" out of the CordovaLib project, and manage the Cordova
> dependency itself as a dynamic framework.
>
> I know this isn't the way most people consume Cordova—the approach is more
> of a traditional native iOS app with hybrid dependencies.  But it also
> doesn't seem like a huge stretch to provide the additional target in the
> CordovaLib project.  It's something we could probably take a look at
> contributing, but I wanted to float the idea to the list first, to get a
> sense of any reservations.
>
> Thanks!
> Kevin
>
>