I do not like to use wine header it exists alot wine specfiy thing in wine header and alot need to change in the header. I did need to rewrite alot of wine header to geting directx port of dinput, dsound and other part. For it did not exists in MinGW headers. You need alot work to rewrite wine header geting this working in reactos. wine header does not work out of the box. I still think the best choice are continue to use mingw headers.
----- Original Message ----- From: "Boaz Harrosh" boaz@hishome.net To: "Rolf Kalbermatter" rolf.kalbermatter@citeng.com; ros-dev@reactos.com; wine-devel@winehq.com Sent: Wednesday, February 23, 2005 2:43 PM Subject: Re: [ros-dev] RE: Collection of wine tools on windows
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.
- ReactOS & MinGW are by themselves GPL, So they are more strict than
Wine's header set 2. Headers are out of the scope for License as Rolf explained. Or to be more precise they are the boundary put by the License. "From this API down you are in Library territory". The header is the Line drawn by the Library writer, as what is public API. A GPL program is an LGPL library with the trivial public header of: <c> int main(int argc ,char* argc[]) ; // use only </c> 3. Wine Headers are description of the Win32 API by Microsoft, so what the hell are you talking about.
And back to the subject. I have proved that Wine-headers are not only, nice-to-have, but a must in a gcc compilation environment on Windows, like MinGW or Cygwin. Could/did any one see if ReactOS has every thing they need in wine-headers and if not patch in the diff.
So is it accepted than!
Free Life Boaz _______________________________________________ Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev