[ros-kernel] Re: Sharing code with wine

[James T. <jim...@ad...>]

Hi,
Casper Hornstrup wrote:
> 
> Porting wine code seem to be the hot topic these days, so I think it is
> time to discuss ways to share code with the wine project before having
> ported most wine code and no (easy) way to update it in the future.
> 

Yeah, sorry that is my fault too.

> FSF would have to grant the wine team permission to use the code.
> 
> Wine modules that I do think is worth porting/sharing:
> 
> gdi32.dll - obviously
> icmp.dll - OS dependent
> kernel32.dll - OS dependent
> ntdll.dll - obviously

> opengl32.dll - wine specific

Off the shelf software? DL from vender and install ~

> user32.dll - we will have calls directly to win32k.sys
> wnaspi32.dll - OS dependent
> all winsock related modules
> 

These should be (with some exceptions) core ROS dll's where the others
make reference to and should stay separate from the wine stuff.

When building comctl32.a and dll you need ntdll.a, kernel32.a, gdi32.a,
user32.a, crtdll.a and msvcrt.a. The next one is comdlg32.a it uses the
same plus comclt32.a and a few others. So we need to sort through the
wine source and determine a build priority tree where one dll depends
on another, etc.. Start reading the makefiles. 8^o More coffee anyone?

> and the 16-bit only DLL's.
> 

I do not think NT is downward compatible is it? The 2k book I have does
say something about it being a options or ?. 

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

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