Manual

46
To do so, aach the following noces to the program. It is safest to aach them to the start of each source le to most eecvely state the exclusion of
warranty; and each le should have at least the “copyright” line and a pointer to where the full noce is found.
<one line to give the program’s name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This program is free soware: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Soware
Foundaon, either version 3 of the License, or
(at your opon) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program. If not, see <hp://www.gnu.org/licenses/>.
Also add informaon on how to contact you by electronic and paper mail.
If the program does terminal interacon, make it output a short noce like this when it starts in an interacve mode:
<program> Copyright (C) <year> <name of author>
This program comes with ABSOLUTELY NO WARRANTY; for details type `show w.
This is free soware, and you are welcome to redistribute it under certain condions; type `show c’ for details.
The hypothecal commands `show w’ and `show c’ should show the appropriate parts of the General Public License. Of course, your program’s commands
might be dierent; for a GUI interface, you would use an “about box.
You should also get your employer (if you work as a programmer) or school, if any, to sign a “copyright disclaimer” for the program, if necessary. For more
informaon on this, and how to apply and follow the GNU GPL, see <hp://www.gnu.org/licenses/>.
The GNU General Public License does not permit incorporang your program into proprietary programs. If your program is a subroune library, you may
consider it more useful to permit linking proprietary applicaons with the library. If this is what you want to do, use the GNU Lesser General Public License
instead of this License. But rst, please read <hp://www.gnu.org/philosophy/why-not-lgpl.html>.
Lesser GNU Public License Version 2.1
sysfsuls
qt
GNU LESSER GENERAL PUBLIC LICENSE
Version 2.1, February 1999
Copyright (C) 1991, 1999 Free Soware Foundaon, Inc.
51 Franklin Street, Fih Floor, Boston, MA 02110-1301 USA
Everyone is permied to copy and distribute verbam copies
of this license document, but changing it is not allowed.
[This is the rst 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.]
Preamble
The licenses for most soware are designed to take away your freedom to share and change it. By contrast, the GNU General Public Licenses are intended
to guarantee your freedom to share and change free soware--to make sure the soware is free for all its users.
This license, the Lesser General Public License, applies to some specially designated soware packages--typically libraries--of the Free Soware Foundaon
and other authors who decide to use it. You can use it too, but we suggest you rst think carefully about whether this license or the ordinary General Public
License is the beer strategy to use in any parcular case, based on the explanaons below.
When we speak of free soware, we are referring to freedom of use, not price. Our General Public Licenses are designed to make sure that you have the
freedom to distribute copies of free soware (and charge for this service if you wish); that you receive source code or can get it if you want it; that you can
change the soware and use pieces of it in new free programs; and that you are informed that you can do these things.
To protect your rights, we need to make restricons that forbid distributors to deny you these rights or to ask you to surrender these rights. These restricons
translate to certain responsibilies for you if you distribute copies of the library or if you modify it.
For example, if you distribute copies of the library, whether gras or for a fee, you must give the recipients all the rights that we gave you. You must make sure
that they, too, receive or can get the source code. If you link other code with the library, you must provide complete object les to the recipients, so that they
can relink them with the library aer making changes to the library and recompiling it. And you must show them these terms so they know their rights.
We protect your rights with a two-step method: (1) we copyright the library, and (2) we oer you this license, which gives you legal permission to copy,
distribute and/or modify the library.