Sage-Tips

Can I use LGPL in commercial software?

You can use and distribute LGPL libraries on your website and use them in combination with commercial code. The only big restriction is that you must keep the library open source, including any modifications you make to it, and allow your users to obtain the source, licence and copyright information for the library.

Can I copy LGPL code?

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. This version of the GNU Lesser General Public License incorporates the terms and conditions of version 3 of the GNU General Public License, supplemented by the additional permissions listed below.

How GPL is different from LGPL software license?

In brief: GPL is mostly for programs while LGPL is limited to software libraries. Whenever changes are made under GPL license, source codes are required and changes must also be licensed under GPL, while LGPL may allow non-GPL programs to link to libraries but must still provide source codes.

Can other developers use the LGPL code?

Other developers can borrow and modify the code and re-distribute it as part of their own project, provided that the portion used under the LGPL, including any modifications, is re-licensed under the LGPL. Other portions of the project are permitted have other licenses.

How to link an LGPL library to an application?

If you are statically linking the LGPL library then you need to provide the source of the library and either the source or object code of your application.

What is the difference between GPL and LGPL license?

If you use a library that is GPL, and you link with that library, your software must be released with a compatible license. If you use a library that is LGPL, and you dynamically link with that library, your software does not have to be released with a compatible license, but you must still comply with the LGPL.

What else needs to be done to get LGPL to work?

If not, what else needs to be done? LGPL’s basic requirement is to separate the LGPL-licensed library and your own product well enough. That should allow users to supply their own version of the library instead of the one you’ve shipped with your software (with the bugs fixed, for instance).