User Manual

However, linking a "work that uses the Library" with the Library create
s an executable that is a derivative of the Library (because it contains
portions of the Library), rather than a "work that uses the library". The
executable is therefore covered by this License. Section 6 states terms
for distribution of such executables.
When a "work that uses the Library" uses material from a header file t
hat is part of the Library, the object code for the work may be a deriva
tive work of the Library even though the source code is not. Whether t
his is true is especially significant if the work can be linked without the
Library, or if the work is itself a library. The threshold for this to be tru
e is not precisely defined by law.
If such an object file uses only numerical parameters, data structure la
youts and accessors, and small macros and small inline functions (ten l
ines or less in length), then the use of the object file is unrestricted, re
gardless of whether it is legally a derivative work. (Executables contain
ing this object code plus portions of the Library will still fall under Secti
on 6.)
Otherwise, if the work is a derivative of the Library, you may distribute
the object code for the work under the terms of Section 6. Any execut
ables containing that work also fall under Section 6, whether or not th
ey are linked directly with the Library itself.
6. As an exception to the Sections above, you may also combine or lin
k a "work that uses the Library" with the Library to produce a work co
ntaining portions of the Library, and distribute that work under terms
of your choice, provided that the terms permit modification of the wor
k for the customer's own use and reverse engineering for debugging s
uch modifications.
You must give prominent notice with each copy of the work that the Li
brary is used in it and that the Library and its use are covered by this
License. You must supply a copy of this License. If the work during ex
ecution displays copyright notices, you must include the copyright noti
ce for the Library among them, as well as a reference directing the use
r to the copy of this License. Also, you must do one of these things:
a) Accompany the work with the complete corresponding machine-rea
dable source code for the Library including whatever changes were us
ed in the work (which must be distributed under Sections 1 and 2 abo
ve); and, if the work is an executable linked with the Library, with the
complete machine-readable "work that uses the Library", as object co
de and/or source code, so that the user can modify the Library and th
en relink to produce a modified executable containing the modified Libr
ary. (It is understood that the user who changes the contents of defini
tions files in the Library will not necessarily be able to recompile the ap
plication to use the modified definitions.)
b) Use a suitable shared library mechanism for linking with the Librar
y. A suitable mechanism is one that (1) uses at run time a copy of the
library already present on the user's computer system, rather than cop
ying library functions into the executable, and (2) will operate properly
with a modified version of the library, if the user installs one, as long a
s the modified version is interface-compatible with the version that the
work was made with.