On Fri, Aug 12, 2011 at 7:21 AM, Matt Lamari <matt.lam...@gmail.com> wrote:
> Assumptions:
> 1. iPhone apps must statically link libraries, can't use dynamic linking
>
Who cares? LGPL does not talk about dynamic or static linking separately. It
talks about libraries and linking.
> 2. An ECL-using iPhone App will need to link in ECL runtime elements.
>
No problem. Build a version of ECL that is statically linked. The iOS port
supports this.
> 3. Apple would pass the app and let it onto the App store.
>
This is not our business but I doubt there is any problem about this, for
commercial use of LGPL software is not forbidden.
> With these assumptions, say an app, FoobarBlasters, was made with ECL
> and put on the app store. . . .
> Is compliance with ECL licensing possible at this stage - if so, what
> would that take? [...]
> Published FoobarBlasters binary that can be dynamically linked with a
> dynamic ECL (not possible if assumption correct).
>
Remove "dynamic" and you'll have it. You only need to provide a version of
your program, typically as a statically linked library, that somebody else
may link with another version of ECL's library. Note that in order to
perform this linkage *no source* is needed. The linker does not need header
files, just a compatible binary.
Juanjo
--
Instituto de Física Fundamental, CSIC
c/ Serrano, 113b, Madrid 28006 (Spain)
http://juanjose.garciaripoll.googlepages.com
------------------------------------------------------------------------------
Get a FREE DOWNLOAD! and learn more about uberSVN rich system,
user administration capabilities and model configuration. Take
the hassle out of deploying and managing Subversion and the
tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2
_______________________________________________
Ecls-list mailing list
Ecls-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecls-list
