What is the main difference between the GNU General Public license and the GNU Lesser General Public license?

What is the main difference between the GNU General Public license and the GNU Lesser General Public license?

One is the GNU Lesser GPL; the other is the ordinary GNU GPL. The choice of license makes a big difference: using the Lesser GPL permits use of the library in proprietary programs; using the ordinary GPL for a library makes it available only for free programs.

Is LGPL compatible with GPL?

Note that the LGPL is compatible with the GPL: you can decide to “upgrade” to GPL and incorporate it in a wholly GPL licensed project if you wish. You can’t however go the other way and re-license GPL licensed code as LGPL.

Is GPL OK for commercial use?

Software under the GPL may be run for all purposes, including commercial purposes and even as a tool for creating proprietary software, such as when using GPL-licensed compilers. Users or companies who distribute GPL-licensed works (e.g. software), may charge a fee for copies or give them free of charge.

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 I use GNU Lesser General Public License?

The license allows developers and companies to use and integrate a software component released under the LGPL into their own (even proprietary) software without being required by the terms of a strong copyleft license to release the source code of their own components. …

Can I statically link LGPL?

You can statically link proprietary code to LGPL libraries and the LGPL license does not “infect” your proprietary code. The only thing you have to do if you go this route is ensure that the people receiving your combined work are able to relink any modified version of the LGPL pieces.

Can I stop others from using my program under the terms of GPL?

The GPL does not require you to release your modified version, or any part of it. You are free to make modifications and use them privately, without ever releasing them.

Can a GPL be enforced?

But it is sometimes said that the GPL can’t be enforced because users haven’t “accepted” it. After all, the GPL requires each copy of covered software to include the license text, so everyone is fully informed. Despite the FUD, as a copyright license the GPL is absolutely solid.

Can you distribute LGPL?

The LGPL License: An Overview. Say, your code links to a library licensed under the LGPL. If you were to modify that library and distribute it, then you’d have to release the changes. But if your program simply uses the library, there’s no need to share your source code for your part of the program.

What is GCC runtime library exception?

This GCC Runtime Library Exception (“Exception”) is an additional permission under section 7 of the GNU General Public License, version 3 (“GPLv3”). When you use GCC to compile a program, GCC may combine portions of certain GCC header files and runtime libraries with the compiled program.

Is the LGPL viral?

LGPL only is non-viral if the end user can trivially replace the linked library with their own version.

Does GPL code have to be public?

Does the GPL require that source code of modified versions be posted to the public? The GPL does not require you to release your modified version. You are free to make modifications and use them privately, without ever releasing them.

What is the Lesser GPL?

[This is the first released version of the Lesser GPL. It also counts as the successor of the GNU Library Public License, version 2, hence the version number 2.1.] The licenses for most software are designed to take away your freedom to share and change it.

What is GNU Lesser general public license (LGPL)?

The GNU Lesser General Public License v2.1 (LGPL v2.1 for short) is a variation of the regular GNU General Public License (GPL).

Should I use the GPL or a more permissive license?

Using the GNU GPL will require that all the released improved versions be free software. This means you can avoid the risk of having to compete with a proprietary modified version of your own work. However, in some special situations it can be better to use a more permissive license.

Will you make an exception for a GNU program under the GPL?

Using a certain GNU program under the GPL does not fit our project to make proprietary software. Will you make an exception for us? It would mean more users of that program. If a programming language interpreter is released under the GPL, does that mean programs written to be interpreted by it must be under GPL-compatible licenses?