Re: [ros-dev] RE: Collection of wine tools on windows

[Filip Navara]

Casper Hornstrup wrote:

>   
>
>   
>
> >  -----Original Message-----
> > From: ros-dev-bounces(a)reactos.com 
> > [mailto:[e-mail]] On Behalf Of Steven Edwards
> > Sent: 21. februar 2005 21:52
> > To: ReactOS Development List; ivanleo(a)gmail.com; wine-devel(a)winehq.com
> > Cc: ros-dev(a)reactos.com
> > Subject: Re: [ros-dev] RE: Collection of wine tools on windows
> >
> > Hi,
> >
> > --- Casper Hornstrup <ch(a)csh-consult.dk> wrote:
> >     
> >
> > >  I might vote for using WINE headers in ReactOS if
> > > WINE 
> > >       
> > >  
> > relicensed its 
> >     
> >
> > >  headers to a w32api or BSD like license that will
> > > allow use in a 
> > > non-free application. What I would like to see most though, 
> > >       
> > >  
> > is for all 
> >     
> >
> > >  three projects to share w32api.
> > >       
> > >  
> > What do you mean? The headers are LGPL so you can use them in 
> > a non-free application.
> >
> > Thanks
> > Steven
> >     
> >  
> Yes, but then you need to publish the sources for the non-free application
> under the LGPL. When using headers to build your application, you create a
> derived work of those headers.
>
> http://www.fsf.org/licensing/licenses/lgpl.html
>
> "A "work based on the Library" means either the Library or any derivative
> work under copyright law: that is to say, a work
> containing the Library or a portion of it, either verbatim or with modifications and/or
> translated straightforwardly into another
> language. (Hereinafter, translation is included without limitation in the term
> "modification".)"
>
> "4. You may copy and distribute the Library (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."
>   
>  
"When a "work that uses the Library" uses material from a header
file
that is part of the Library, the object code for the work may be a
derivative work of the Library even though the source code is not.
Whether this 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 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 portions of the
Library will still fall under Section 6.)"

- Filip