8
Section 6 states te rms for distrib ution of such execut ables.
When a “work that uses t he Library” u ses material fro m a header le that is par t of the Librar y, the object
code for the work may be a der ivative work of the L ibrary even tho ugh the source code is not .
Whether this is tru e is especially signi cant if the work ca n be linked without t he Library, or if th e work is
itself a librar y. The threshold for thi s to be true is not preci sely dened by law.
If such an object le use s only numerical pa rameters, d ata structu re layouts and access ors, and small
macros and small inline f unctions (ten line s or less in length), the n the use of the object  le is unrestri cted,
regardless of wheth er it is legally a der ivative work . (Executables co ntaining this obje ct code plus port ions of
the Library will s till fall under Se ction 6.)
Otherwise, if t he work is a deriva tive of the Librar y, you may distribut e the object code for th e work under
the terms of Section 6 .
Any executables cont aining that work als o fall under Secti on 6, whether or not t hey are linked dire ctly with
the Library it self.
6. As an exception to the Sec tions above, you may als o combine or link a “wor k that uses the Libr ary” with
the Library to pr oduce a work containi ng portions of the L ibrary, and dis tribute that wor k under terms
of your choice, provided t hat the terms per mit modication of t he work for the custo mer’s own use and
reverse engineer ing for debugging s uch modications .
You must give prominent not ice with each copy of the wor k that the Librar y is used in it and tha t the
Library and it s use are covered by this L icense. You must supply a co py of this License. If the w ork during
execution displays copy right notices, you mu st include the copyr ight notice for the Li brary among th em, as
well as a reference dir ecting the user to th e copy of this License. Al so, you must do one of thes e things:
a) Accompany the work wit h the complete corr esponding machine -readable sour ce code for the Librar y
including whatever cha nges were used in the wor k (which must be dis tributed unde r Sections 1
and 2 above); and, if the work is a n executable linke d with the Libra ry, with the comple te machine-
readable “work tha t uses the Librar y”, as object code and /or source code, so that t he user can modify
the Library and t hen relink to produ ce a modied executa ble containing the m odied Librar y. (It is
understood that t he user who changes th e contents of denit ions les in the Libr ary will not neces sarily
be able to recompile the a pplication to use th e modied deniti ons.)
b) Use a suitable shared lib rary mechanis m for linking with t he Library. A sui table mechanism is o ne that
(1) uses at run time a copy of the libr ary already pr esent on the user’s co mputer system , rather than
copying library fu nctions into the exe cutable, and (2) wil l operate proper ly with a modied ve rsion
of the library, if the us er installs one, a s long as the modie d version is inter face-compatib le with the
version that the wor k was made with.
c) Accompany the work wi th a written off er, valid for at least th ree years, to give t he same user the
materials specie d in Subsection 6a , above, for a charge no m ore than the cost of per forming this
distribution.
d) If distribution of the wo rk is made by offeri ng access to copy from a desig nated place, offer e quivalent
access to copy the above speci ed materials fro m the same place.
e) Verify that the user has a lready received a co py of these materials o r that you have already se nt this
user a copy.
For an executable, th e required form of t he “work that uses t he library” mu st include any data a nd utility
programs needed for r eproducing the ex ecutable from it . However, as a special exce ption, the mater ials to
be distributed ne ed not include anyt hing that is normall y distribute d (in either source o r binary form) with
the major components (comp iler, kernel, and so on) of th e operating sys tem on which the execu table runs,
unless that component i tself accompanie s the executable .
It may happen that this re quirement contr adicts the lice nse restrict ions of other propr ietary libr aries that do
not normally accompany t he operating sys tem. Such a contra diction means you c annot use both them an d
the Library toge ther in an executab le that you distri bute.
7. You may place libr ary facilities t hat are a work based o n the Library s ide-by-side in a sin gle library tog ether
with other librar y facilities not cove red by this License, a nd distribut e such a combined libr ary, provided that
the separate dist ribution of the wor k based on the Libr ary and of the othe r library facil ities is otherw ise
permitted, and p rovided that you do th ese two things:
a) Accompany the combined li brary with a co py of the same work base d on the Librar y, uncombined with
any other library f acilities. This m ust be distrib uted under the ter ms of the Sections a bove.
b) Give prominent notice wit h the combined libr ary of the fact th at part of it is a wor k based on the
Library, and expla ining where to nd th e accompanying uncomb ined form of the same wo rk.