0
+ GNU LESSER GENERAL PUBLIC LICENSE
0
+ Version 2.1, February 1999
0
+ Copyright (C) 1991, 1999 Free Software Foundation, Inc.
0
+ 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
0
+ Everyone is permitted to copy and distribute verbatim copies
0
+ of this license document, but changing it is not allowed.
0
+[This is the first released version of the Lesser GPL. It also counts
0
+ as the successor of the GNU Library Public License, version 2, hence
0
+ the version number 2.1.]
0
+ The licenses for most software are designed to take away your
0
+freedom to share and change it. By contrast, the GNU General Public
0
+Licenses are intended to guarantee your freedom to share and change
0
+free software--to make sure the software is free for all its users.
0
+ This license, the Lesser General Public License, applies to some
0
+specially designated software packages--typically libraries--of the
0
+Free Software Foundation and other authors who decide to use it. You
0
+can use it too, but we suggest you first think carefully about whether
0
+this license or the ordinary General Public License is the better
0
+strategy to use in any particular case, based on the explanations below.
0
+ When we speak of free software, we are referring to freedom of use,
0
+not price. Our General Public Licenses are designed to make sure that
0
+you have the freedom to distribute copies of free software (and charge
0
+for this service if you wish); that you receive source code or can get
0
+it if you want it; that you can change the software and use pieces of
0
+it in new free programs; and that you are informed that you can do
0
+ To protect your rights, we need to make restrictions that forbid
0
+distributors to deny you these rights or to ask you to surrender these
0
+rights. These restrictions translate to certain responsibilities for
0
+you if you distribute copies of the library or if you modify it.
0
+ For example, if you distribute copies of the library, whether gratis
0
+or for a fee, you must give the recipients all the rights that we gave
0
+you. You must make sure that they, too, receive or can get the source
0
+code. If you link other code with the library, you must provide
0
+complete object files to the recipients, so that they can relink them
0
+with the library after making changes to the library and recompiling
0
+it. And you must show them these terms so they know their rights.
0
+ We protect your rights with a two-step method: (1) we copyright the
0
+library, and (2) we offer you this license, which gives you legal
0
+permission to copy, distribute and/or modify the library.
0
+ To protect each distributor, we want to make it very clear that
0
+there is no warranty for the free library. Also, if the library is
0
+modified by someone else and passed on, the recipients should know
0
+that what they have is not the original version, so that the original
0
+author's reputation will not be affected by problems that might be
0
+ Finally, software patents pose a constant threat to the existence of
0
+any free program. We wish to make sure that a company cannot
0
+effectively restrict the users of a free program by obtaining a
0
+restrictive license from a patent holder. Therefore, we insist that
0
+any patent license obtained for a version of the library must be
0
+consistent with the full freedom of use specified in this license.
0
+ Most GNU software, including some libraries, is covered by the
0
+ordinary GNU General Public License. This license, the GNU Lesser
0
+General Public License, applies to certain designated libraries, and
0
+is quite different from the ordinary General Public License. We use
0
+this license for certain libraries in order to permit linking those
0
+libraries into non-free programs.
0
+ When a program is linked with a library, whether statically or using
0
+a shared library, the combination of the two is legally speaking a
0
+combined work, a derivative of the original library. The ordinary
0
+General Public License therefore permits such linking only if the
0
+entire combination fits its criteria of freedom. The Lesser General
0
+Public License permits more lax criteria for linking other code with
0
+ We call this license the "Lesser" General Public License because it
0
+does Less to protect the user's freedom than the ordinary General
0
+Public License. It also provides other free software developers Less
0
+of an advantage over competing non-free programs. These disadvantages
0
+are the reason we use the ordinary General Public License for many
0
+libraries. However, the Lesser license provides advantages in certain
0
+ For example, on rare occasions, there may be a special need to
0
+encourage the widest possible use of a certain library, so that it becomes
0
+a de-facto standard. To achieve this, non-free programs must be
0
+allowed to use the library. A more frequent case is that a free
0
+library does the same job as widely used non-free libraries. In this
0
+case, there is little to gain by limiting the free library to free
0
+software only, so we use the Lesser General Public License.
0
+ In other cases, permission to use a particular library in non-free
0
+programs enables a greater number of people to use a large body of
0
+free software. For example, permission to use the GNU C Library in
0
+non-free programs enables many more people to use the whole GNU
0
+operating system, as well as its variant, the GNU/Linux operating
0
+ Although the Lesser General Public License is Less protective of the
0
+users' freedom, it does ensure that the user of a program that is
0
+linked with the Library has the freedom and the wherewithal to run
0
+that program using a modified version of the Library.
0
+ The precise terms and conditions for copying, distribution and
0
+modification follow. Pay close attention to the difference between a
0
+"work based on the library" and a "work that uses the library". The
0
+former contains code derived from the library, whereas the latter must
0
+be combined with the library in order to run.
0
+ GNU LESSER GENERAL PUBLIC LICENSE
0
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0
+ 0. This License Agreement applies to any software library or other
0
+program which contains a notice placed by the copyright holder or
0
+other authorized party saying it may be distributed under the terms of
0
+this Lesser General Public License (also called "this License").
0
+Each licensee is addressed as "you".
0
+ A "library" means a collection of software functions and/or data
0
+prepared so as to be conveniently linked with application programs
0
+(which use some of those functions and data) to form executables.
0
+ The "Library", below, refers to any such software library or work
0
+which has been distributed under these terms. A "work based on the
0
+Library" means either the Library or any derivative work under
0
+copyright law: that is to say, a work containing the Library or a
0
+portion of it, either verbatim or with modifications and/or translated
0
+straightforwardly into another language. (Hereinafter, translation is
0
+included without limitation in the term "modification".)
0
+ "Source code" for a work means the preferred form of the work for
0
+making modifications to it. For a library, complete source code means
0
+all the source code for all modules it contains, plus any associated
0
+interface definition files, plus the scripts used to control compilation
0
+and installation of the library.
0
+ Activities other than copying, distribution and modification are not
0
+covered by this License; they are outside its scope. The act of
0
+running a program using the Library is not restricted, and output from
0
+such a program is covered only if its contents constitute a work based
0
+on the Library (independent of the use of the Library in a tool for
0
+writing it). Whether that is true depends on what the Library does
0
+and what the program that uses the Library does.
0
+ 1. You may copy and distribute verbatim copies of the Library's
0
+complete source code as you receive it, in any medium, provided that
0
+you conspicuously and appropriately publish on each copy an
0
+appropriate copyright notice and disclaimer of warranty; keep intact
0
+all the notices that refer to this License and to the absence of any
0
+warranty; and distribute a copy of this License along with the
0
+ You may charge a fee for the physical act of transferring a copy,
0
+and you may at your option offer warranty protection in exchange for a
0
+ 2. You may modify your copy or copies of the Library or any portion
0
+of it, thus forming a work based on the Library, and copy and
0
+distribute such modifications or work under the terms of Section 1
0
+above, provided that you also meet all of these conditions:
0
+ a) The modified work must itself be a software library.
0
+ b) You must cause the files modified to carry prominent notices
0
+ stating that you changed the files and the date of any change.
0
+ c) You must cause the whole of the work to be licensed at no
0
+ charge to all third parties under the terms of this License.
0
+ d) If a facility in the modified Library refers to a function or a
0
+ table of data to be supplied by an application program that uses
0
+ the facility, other than as an argument passed when the facility
0
+ is invoked, then you must make a good faith effort to ensure that,
0
+ in the event an application does not supply such function or
0
+ table, the facility still operates, and performs whatever part of
0
+ its purpose remains meaningful.
0
+ (For example, a function in a library to compute square roots has
0
+ a purpose that is entirely well-defined independent of the
0
+ application. Therefore, Subsection 2d requires that any
0
+ application-supplied function or table used by this function must
0
+ be optional: if the application does not supply it, the square
0
+ root function must still compute square roots.)
0
+These requirements apply to the modified work as a whole. If
0
+identifiable sections of that work are not derived from the Library,
0
+and can be reasonably considered independent and separate works in
0
+themselves, then this License, and its terms, do not apply to those
0
+sections when you distribute them as separate works. But when you
0
+distribute the same sections as part of a whole which is a work based
0
+on the Library, the distribution of the whole must be on the terms of
0
+this License, whose permissions for other licensees extend to the
0
+entire whole, and thus to each and every part regardless of who wrote
0
+Thus, it is not the intent of this section to claim rights or contest
0
+your rights to work written entirely by you; rather, the intent is to
0
+exercise the right to control the distribution of derivative or
0
+collective works based on the Library.
0
+In addition, mere aggregation of another work not based on the Library
0
+with the Library (or with a work based on the Library) on a volume of
0
+a storage or distribution medium does not bring the other work under
0
+the scope of this License.
0
+ 3. You may opt to apply the terms of the ordinary GNU General Public
0
+License instead of this License to a given copy of the Library. To do
0
+this, you must alter all the notices that refer to this License, so
0
+that they refer to the ordinary GNU General Public License, version 2,
0
+instead of to this License. (If a newer version than version 2 of the
0
+ordinary GNU General Public License has appeared, then you can specify
0
+that version instead if you wish.) Do not make any other change in
0
+ Once this change is made in a given copy, it is irreversible for
0
+that copy, so the ordinary GNU General Public License applies to all
0
+subsequent copies and derivative works made from that copy.
0
+ This option is useful when you wish to copy part of the code of
0
+the Library into a program that is not a library.
0
+ 4. You may copy and distribute the Library (or a portion or
0
+derivative of it, under Section 2) in object code or executable form
0
+under the terms of Sections 1 and 2 above provided that you accompany
0
+it with the complete corresponding machine-readable source code, which
0
+must be distributed under the terms of Sections 1 and 2 above on a
0
+medium customarily used for software interchange.
0
+ If distribution of object code is made by offering access to copy
0
+from a designated place, then offering equivalent access to copy the
0
+source code from the same place satisfies the requirement to
0
+distribute the source code, even though third parties are not
0
+compelled to copy the source along with the object code.
0
+ 5. A program that contains no derivative of any portion of the
0
+Library, but is designed to work with the Library by being compiled or
0
+linked with it, is called a "work that uses the Library". Such a
0
+work, in isolation, is not a derivative work of the Library, and
0
+therefore falls outside the scope of this License.
0
+ However, linking a "work that uses the Library" with the Library
0
+creates an executable that is a derivative of the Library (because it
0
+contains portions of the Library), rather than a "work that uses the
0
+library". The executable is therefore covered by this License.
0
+Section 6 states terms for distribution of such executables.
0
+ When a "work that uses the Library" uses material from a header file
0
+that is part of the Library, the object code for the work may be a
0
+derivative work of the Library even though the source code is not.
0
+Whether this is true is especially significant if the work can be
0
+linked without the Library, or if the work is itself a library. The
0
+threshold for this to be true is not precisely defined by law.
0
+ If such an object file uses only numerical parameters, data
0
+structure layouts and accessors, and small macros and small inline
0
+functions (ten lines or less in length), then the use of the object
0
+file is unrestricted, regardless of whether it is legally a derivative
0
+work. (Executables containing this object code plus portions of the
0
+Library will still fall under Section 6.)
0
+ Otherwise, if the work is a derivative of the Library, you may
0
+distribute the object code for the work under the terms of Section 6.
0
+Any executables containing that work also fall under Section 6,
0
+whether or not they are linked directly with the Library itself.
0
+ 6. As an exception to the Sections above, you may also combine or
0
+link a "work that uses the Library" with the Library to produce a
0
+work containing portions of the Library, and distribute that work
0
+under terms of your choice, provided that the terms permit
0
+modification of the work for the customer's own use and reverse
0
+engineering for debugging such modifications.
0
+ You must give prominent notice with each copy of the work that the
0
+Library is used in it and that the Library and its use are covered by
0
+this License. You must supply a copy of this License. If the work
0
+during execution displays copyright notices, you must include the
0
+copyright notice for the Library among them, as well as a reference
0
+directing the user to the copy of this License. Also, you must do one
0
+ a) Accompany the work with the complete corresponding
0
+ machine-readable source code for the Library including whatever
0
+ changes were used in the work (which must be distributed under
0
+ Sections 1 and 2 above); and, if the work is an executable linked
0
+ with the Library, with the complete machine-readable "work that
0
+ uses the Library", as object code and/or source code, so that the
0
+ user can modify the Library and then relink to produce a modified
0
+ executable containing the modified Library. (It is understood
0
+ that the user who changes the contents of definitions files in the
0
+ Library will not necessarily be able to recompile the application
0
+ to use the modified definitions.)
0
+ b) Use a suitable shared library mechanism for linking with the
0
+ Library. A suitable mechanism is one that (1) uses at run time a
0
+ copy of the library already present on the user's computer system,
0
+ rather than copying library functions into the executable, and (2)
0
+ will operate properly with a modified version of the library, if
0
+ the user installs one, as long as the modified version is
0
+ interface-compatible with the version that the work was made with.
0
+ c) Accompany the work with a written offer, valid for at
0
+ least three years, to give the same user the materials
0
+ specified in Subsection 6a, above, for a charge no more
0
+ than the cost of performing this distribution.
0
+ d) If distribution of the work is made by offering access to copy
0
+ from a designated place, offer equivalent access to copy the above
0
+ specified materials from the same place.
0
+ e) Verify that the user has already received a copy of these
0
+ materials or that you have already sent this user a copy.
0
+ For an executable, the required form of the "work that uses the
0
+Library" must include any data and utility programs needed for
0
+reproducing the executable from it. However, as a special exception,
0
+the materials to be distributed need not include anything that is
0
+normally distributed (in either source or binary form) with the major
0
+components (compiler, kernel, and so on) of the operating system on
0
+which the executable runs, unless that component itself accompanies
0
+ It may happen that this requirement contradicts the license
0
+restrictions of other proprietary libraries that do not normally
0
+accompany the operating system. Such a contradiction means you cannot
0
+use both them and the Library together in an executable that you
0
+ 7. You may place library facilities that are a work based on the
0
+Library side-by-side in a single library together with other library
) is private.
