[ros-kernel] Re: Sharing code with wine

[Phillip S. <ps...@cf...>]

At 07:21 PM 10/24/2001 +0200, you wrote:
>It has been mentioned on the ros-kernel list to use mingw headers
>instead
>of having separate headers due to the fact that 1) mingw headers have a
>greater chance of beeing updated more often 2) The mingw team could
>benefit
>from these headers (the ntddk case). Another possibillity is to have our
>own
>version of the Windows headers shared with wine.

I agree with merging our headers with mingw.

>I'm leaning towards the former - using mingw headers. This way may mean
>more
>work when updating shared wine code, because if there is a change in
>public
>Windows headers, both set of headers needs to be updated (wine and
>mingw).
>Of course, we could just do it properly from the start and implement the
>full
>set of Windows headers. Then this will not be a problem ;o)
>
>Wine modules that I do think is worth porting/sharing:
>
>gdi32.dll - obviously

Negative.  Wine's gdi32.dll implementation is completely different from 
ours.  Theirs does funky things to implement drawing on an X display, ours 
basically calls down to kernel mode where it is implemented in win32k.sys 
using DDI display drivers.

>icmp.dll - OS dependent
>kernel32.dll - OS dependent

Also reactos specific, or is that what you mean by OS specific?

>ntdll.dll - obviously

Again, no.  I don't even think that WINE has an ntdll, and ours is just a 
stub to call into the kernel.

>opengl32.dll - wine specific
>user32.dll - we will have calls directly to win32k.sys

Right, same as gdi32.

>wnaspi32.dll - OS dependent

I don't think we need to implement this one at all, it comes with most 
burner software ( which is the only thing that I know of that uses the darn 
POS ), and from my experience, they only work with the version that they 
come with.

>all winsock related modules

Also not going to be shared.  Our winsock dlls are going to make calls down 
to afd.sys in the kernel, wine's will make bsd sockets calls to the linux 
kernel.


>and the 16-bit only DLL's.

Does wine support 16bit apps?  We don't, and I don't see any need to 
either.  It has been many many years since we left the 16bit world 
behind.  We finally even got rid of the ISA bus.  I think we can drop 16bit 
windows/dos as well.


>Let's discuss this topic and propose a plan for code integration to the
>wine developers.
>
>- Casper

====================================================
= To remove yourself from this mailing list, go to =
= http://www.reactos.com/home/mailing.html         =
====================================================