A quick, understandable, summary of the license is often provided on
tldrlegal, for LGPL 2.1 - here -

Your own software can have any license (incl. being closed source), while
using LGPL libraries. You are required to provide license and source code
of those libraries (and any modifications of them). This is often done by
adding licenses into your installer and providing source code of the
libraries on your distribution media (if I'm not mistaken for LGLP 2.1
including just a link to your upstream project is not enough).

In short, you don't need to open source your own program at all (it can
have any license), but you need to make GTK+-3 source available (and any
modifications to it) and let user agree on its licenses when installing
your software.

On Mon, Feb 25, 2019 at 6:25 PM ? ?? via gtk-list <gtk-list@gnome.org>

> I want to develop a program with gtk+3, and gtk+3 is under gnu lgpl2.1.
> Should I open-source my program if I use the library by linking the library
> in compile-time(such as #pragma comment(lib, “xxx.lib”) in visual studio).
> If I must, how can I avoid open-source my program by using gtk+3?
> Thanks you very much.
> Alex Cui
> 2019.2.25
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
> Windows 10
> _______________________________________________
> gtk-list mailing list
> gtk-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/gtk-list
gtk-list mailing list

Reply via email to