I am not a lawyer, and what I say below might be incorrect. Best to consult
a lawyer/licensing expert. I think the Free Software Foundation and EFF
might be able to clarify your doubts.
I believe the LGPL specifies that you have to provide the source code
corresponding to the binary/object file you are shipping, so just providing
a link to ice4j project won't do.
If you've made modifications to ice4j, you will have to release source code
of the modified version, so you should host it somewhere and provide links
to it. If you haven't modified it in any way, then you can just provide a
link to the original source code version corresponding to what you've
I believe the LGPL doesn't require you to ship source code along with the
compiled binaries/object files. It just requires you to provide the
modifications to the source code if any (under the same license).
I hope this helped.
On Wed, Jul 9, 2014 at 7:36 AM, Yaman Corrupt <email@example.com> wrote:
To whom it may concern,
I understand that Ice4j is licensed under LGPL, but I don't understand the
implications. Using LGPL libraries in android apps seems to be a gray area.
LGPL requires that source code for LGPL libraries be included in official
distributions, however, it seems a waste of time to include the source in
my app when no one will want to look at it. I will put a notice similar to
the one below in my final distribution, along with the rest of the licenses
for 3rd party libraries:
This app uses Ice4j, which is distributed under LGPLv3.
A copy of this license may be found at
The full source code of Ice4j may be found at
Is this enough to comply with LGPL, or do I need explicit permission from
Jitsi to use Ice4j in my app?
dev mailing list
Unsubscribe instructions and other list options: