[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [fluid-dev] Android & LGPL

From: Erik Fros
Subject: Re: [fluid-dev] Android & LGPL
Date: Tue, 08 Jan 2013 00:21:43 +0200
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0

Thanks! This is exactly my understanding of that. Compilation of FluidSynth as separate dynamic .so library meets that requirements. I can dynamically load it and
invoke FluidSynth api right from Android app.
Too pitty that it couldn't be achieved for iOS and I have to find some alternative packages for it. Do you know any commercial synth libs for iOS?


On 07.01.13 23:56, Element Green wrote:
On Mon, Jan 7, 2013 at 10:42 AM, Erik Fros <address@hidden> wrote:
Hi everyone,

I've found the link to page LicensingFAQ which covers only iOS:

It makes sense that you can't use it for iOS due-to restriction of static linking. Situation with Android is a little bit different - you can build library as .so (e.g.
fluidsynth.so) and link it dynamically using Android NDK + JNI. How do you think does it violate license?

Best Regards,

This has been discussed several times on this list.

In summary:

LGPL allows for a distributed commercial closed source application to dynamically link to an LGPL licensed library, as long as the LGPL source code is made publicly available, at a minimum in the event that someone requests it, whether it has been modified or not.  If any modifications have been made to the LGPL code, these modifications must also be made publicly available.

Of note, is that commercial static linking to an LGPL library can also be in compliance, so long as the commercial application is distributed in a form that allow an end user to link to a possibly newer version of the LGPL library.  This can be accomplished by distributing the commercial application as an object file as well.

Best regards,

Element Green

fluid-dev mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]