RE: Collection of wine tools on windows

[Casper Hornstrup]

> -----Original Message-----
> From: [e-mail] 
> [mailto:[e-mail]] On Behalf Of Ivan Leo Puoti
> Sent: 21. februar 2005 09:26
> To: [e-mail]
> Cc: [e-mail]
> Subject: Re: Collection of wine tools on windows
>
> Dimitrie O. Paun wrote:
> > Heh, the MinGW folks seem to have some strange
>
> requirements for their
> > headers, I don't think they'll drop theirs. But we can
>
> start by having
> > ReactOS adopt our headers.
> >
> > We should also offer our headers as a separate package that
>
> works out
> > of the box as a replacement for the MinGW ones. This way people can 
> > just get our headers if they are better than the MinGW ones.
>
> Can't the win32api package headers be used to replace the 
> mingw headers?
>
> Ivan.

W32api IS the MinGW headers.

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.

Casper

[Steven Edwards]

Hi,

--- Casper Hornstrup [e-mail] 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

__________________________________ 
Do you Yahoo!? 
Take Yahoo! Mail with you! Get it on your mobile phone. 
http://mobile.yahoo.com/maildemo

[Casper Hornstrup]

> -----Original Message-----
> From: [e-mail] 
> [mailto:[e-mail]] On Behalf Of Steven Edwards
> Sent: 21. februar 2005 21:52
> To: ReactOS Development List; [e-mail]; [e-mail]
> Cc: [e-mail]
> Subject: Re: [ros-dev] RE: Collection of wine tools on windows
>
> Hi,
>
> --- Casper Hornstrup [e-mail] 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."

Casper

[Steven Edwards]

--- Casper Hornstrup [e-mail] wrote:
> 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

The headers are a public interface and as such only the phsical copy of the header falls under
that sort of restriction. Go check out the GTK/GLIB headers. Both of which were developed for
GNOME under the eye of the free software foundation. 1000s of closed source applications are
developed using GTK/GLIB and there is no question that YES you can use them in a closed source
application provided you make a offer for your changes to GTK/GLIB. The Wine people consulted the
FSF and other projects before moving to the LGPL and having the headers under the LGPL is not a
problem.

Thanks
Steven

__________________________________ 
Do you Yahoo!? 
Read only the mail you want - Yahoo! Mail SpamGuard. 
http://promotions.yahoo.com/new_mail

[Filip Navara]

Casper Hornstrup wrote:
> > -----Original Message-----
> > From: [e-mail] 
> > [mailto:[e-mail]] On Behalf Of Steven Edwards
> > Sent: 21. februar 2005 21:52
> > To: ReactOS Development List; [e-mail]; [e-mail]
> > Cc: [e-mail]
> > Subject: Re: [ros-dev] RE: Collection of wine tools on windows
> >
> > Hi,
> >
> > --- Casper Hornstrup [e-mail] 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