LG 32LF57 Series Owner's Manual page 107

�hus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the
intent is to exercise the right to control the distribution of derivative or collective works based on the �ibrary.
In addition, mere aggregation of another work not based on the �ibrary with the �ibrary (or with a work based on the
�ibrary) on a volume of a storage or distribution medium does not bring the other work under the scope of this �icense.
3. You may opt to apply the terms of the ordinary GNU General Public License instead of this License to a given copy
of the �ibrary. �o do this, you must alter all the notices that refer to this �icense, so that they refer to the ordinary G��
General Public �icense, version 2, instead of to this �icense. (If a newer version than version 2 of the ordinary G��
General Public �icense has appeared, then you can specify that version instead if you wish.) Do not make any other
change in these notices. Once this change is made in a given copy, it is irreversible for that copy, so the ordinary G��
General Public �icense applies to all subsequent copies and derivative works made from that copy.
�his option is useful when you wish to copy part of the code of the �ibrary into a program that is not a library.
4. You may copy and distribute the �ibrary (or a portion or derivative of it, under Section 2) in object code or executable
form under the terms of Sections 1 and 2 above provided that you accompany it with the complete corresponding
machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange.
If distribution of object code is made by offering access to copy from a designated place, then offering equivalent access
to copy the source code from the same place satisfies the requirement to distribute the source code, even though third
parties are not compelled to copy the source along with the object code.
5. A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being
compiled or linked with it, is called a "work that uses the �ibrary". Such a work, in isolation, is not a derivative work of the
�ibrary, and therefore falls outside the scope of this �icense.
However, linking a "work that uses the �ibrary" with the �ibrary creates an executable that is a derivative of the �ibrary
(because it contains portions of the �ibrary), rather than a "work that uses the library". �he executable is therefore
covered by this �icense. Section 6 states terms for distribution of such executables.
When a "work that uses the �ibrary" uses material from a header file that is part of the �ibrary, the object code for the
work may be a derivative work of the �ibrary even though the source code is not. Whether this is true is especially
significant if the work can be linked without the �ibrary, or if the work is itself a library.
�he threshold for this to be true is not precisely defined by law.
If such an object file uses only numerical parameters, data structure layouts and accessors, and small macros and small
inline functions (ten lines or less in length), then the use of the object file is unrestricted, regardless of whether it is legally
a derivative work. (�xecutables containing this object code plus portions of the �ibrary will still fall under Section 6.)
Otherwise, if the work is a derivative of the �ibrary, you may distribute the object code for the work under the terms of
Section 6. Any executables containing that work also fall under Section 6, whether or not they are linked directly with the
�ibrary itself.
6. As an exception to the Sections above, you may also combine or link a "work that uses the �ibrary" with the �ibrary
to produce a work containing portions of the �ibrary, and distribute that work under terms of your choice, provided that
the terms permit modification of the work for the customer's own use and reverse engineering for debugging such
odifications.
You must give prominent notice with each copy of the work that the �ibrary is used in it and that the �ibrary and its use
are covered by this �icense. You must supply a copy of this �icense. If the work during execution displays copyright
notices, you must include the copyright notice for the �ibrary among them, as well as a reference directing the user to the
copy of this �icense. Also, you must do one of these things:
a) Accompany the work with the complete corresponding machine-readable source code for the �ibrary including
whatever changes were used in the work (which must be distributed under Sections 1 and 2 above); and, if the work
is an executable linked with the �ibrary, with the complete machine-readable "work that uses the �ibrary", as object
code and/or source code, so that the user can modify the �ibrary and then relink to produce a modified executable
containing the modified �ibrary. (It is understood that the user who changes the contents of definitions files in the
�ibrary will not necessarily be able to recompile the application to use the modified definitions.)
b) �se a suitable shared library mechanism for linking with the �ibrary. 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 copying library functions into
the executable, and (2) will operate properly with a modified version of the library, if the user installs one, as long as
the modified version is interface-compatible with the version that the work was made with.
GB-105