Rolf Kalbermatter wrote:
This is rubish.
Yes ^ 3 ( that is Yes cubed)
Let us all get back on track of this discussion. Must ReactOS and MinGW
use the Wine set of headers.
1. ReactOS & MinGW are by themselves GPL, So they are more strict than
Wine's header set
2. Headers are out of the scope fo
"Casper Hornstrup" <[EMAIL PROTECTED]> 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
>
>"A "work based
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Steven Edwards
> Sent: 21. februar 2005 21:52
> To: ReactOS Development List; [EMAIL PROTECTED]; wine-devel@winehq.com
> Cc: [EMAIL PROTECTED]
> Subject: Re: [ros-dev] RE: Col
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Ivan Leo Puoti
> Sent: 21. februar 2005 09:26
> To: wine-devel@winehq.com
> Cc: [EMAIL PROTECTED]
> Subject: Re: Collection of wine tools on windows
>
> Dimitrie O. Paun
Casper Hornstrup wrote:
W32api IS the MinGW headers.
No, we have a wine win32 package on our download page, it's build with
wine headers, not the
mingw ones.
Ivan.
--- Casper Hornstrup <[EMAIL PROTECTED]> 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 heade
Hi,
--- Casper Hornstrup <[EMAIL PROTECTED]> 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.
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 th
On Sun, Feb 20, 2005 at 07:48:40PM +0200, Boaz Harrosh wrote:
> 1) MinGW header-set are Evil - Because they are ugly, with this, no
> variables names, and all this style for machines guide. This I already
> carry for 10 years so here it is off my chest.
Heh, the MinGW folks seem to have some str
Hi Boaz,
--- Boaz Harrosh <[EMAIL PROTECTED]> wrote:
> 1) MinGW header-set are Evil - Because they are ugly, with this, no
> variables names, and all this style for machines guide. This I already
> carry for 10 years so here it is off my chest.
Yes they are evil. Alex and I were discussing this
There is a question at the end.
Background:
I'm putting up a Web-corner with ATL & MFC for other (gcc for now)
Compilers. It will include tools, links, documentation, example
makefiles, and so on to let people take an MSVC project and compile it
under GCC. (+Winelib on other than windows platfo
11 matches
Mail list logo
