[Ecls-list] ECL's license and commercial IPhone apps
Juan Jose Garcia-Ripoll
juanjose.garciaripoll at googlemail.com
Wed Aug 17 20:36:03 UTC 2011
On Fri, Aug 12, 2011 at 7:21 AM, Matt Lamari <matt.lamari at gmail.com> wrote:
> 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
> 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.
Instituto de Física Fundamental, CSIC
c/ Serrano, 113b, Madrid 28006 (Spain)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ecl-devel