Philips MCI730 - Инструкция по эксплуатации - Страница 67

Whether this is true is especially significant if the work can be linked without the Librar y, or if the work is 
itself a librar y.  The 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.  (Executables containing this object code plus por tions 
of the Librar y will still fall under Section 6.) 
 
  Otherwise, if the work is a derivative of the Librar y, 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 Librar y itself. 
 
  6. As an exception to the Sections above, you may also compile or link a "work that uses the Librar y" 
with the Librar y to produce a work containing por tions of the Librar y, 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 modifications. 
 
  You must give prominent notice with each copy of the work that the Librar y is used in it and that the 
Librar y and its use are covered by this License.  You must supply a copy of this License.  If the work during 
execution displays copyright notices, you must include the copyright notice for the Librar y among them, as 
well as a reference directing the user to the copy of this License.  Also, you must do one of these things: 
 
    a) Accompany the work with the complete corresponding machine-readable source code for the  
    Librar y 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 Librar y, with the complete machine- 
    readable "work that uses the Librar y", as object code and/or source code, so that the user can modify  
    the Librar y and then relink to produce a modified executable containing the modified Librar y.  (It is  
    understood that the user who changes the contents of definitions files in the Librar y will not  
    necessarily be able to recompile the application to use the modified definitions.) 
 
    b) Accompany the work with a written offer, valid for at least three years, to give the same user the  
    materials specified in Subsection 6a, above, for a charge no more than the cost of performing this  
    distribution. 
 
    c) If distribution of the work is made by offering access to copy from a designated place, offer  
    equivalent access to copy the above specified materials from the same place. 
 
    d) Verify that the user has already received a copy of these materials or that you have already sent this  
    user a copy. 
 
  For an executable, the required form of the "work that uses the Librar y" must include any data and utility 
programs needed for reproducing the executable from it.  However, as a special exception, the source 
code distributed need not include anything that is normally distributed (in either source or binar y form) 
with the major components (compiler, kernel, and so on) of the operating system on which the 
executable runs, unless that component itself accompanies the executable. 
 
  It may happen that this requirement contradicts the license restrictions of other proprietar y libraries that 
do not normally accompany the operating system.  Such a contradiction means you cannot use both them 
and the Librar y together in an executable that you distribute. 
 
  7. You may place librar y facilities that are a work based on the Librar y side-by-side in a single librar y