[ros-kernel] Wine integration

[Filip Navara]

This week I have been working on porting OLE32 and SHLWAPI and it's not as
hard as it seems. I think the main problem with solution 2. is that there is
general lack of commiting patch to w32api CVS and also some developers of
ReactOS don't like checking out/compiling w32api every now and then. Despite
there are some problems with it, I vote for solution 2. if it would be
possible to solve the problem of commiting w32api patches to their CVS.
Otherwise I agree that we have to go with solution nr. 1.

One slightly off-topic question is how to use the wine2ros and winebuild
tools you commited?

Thanks
Filip

----- Original Message ----- 
From: "Casper Hornstrup" <chorns at users.sourceforge.net>
To: "'ReactOS Kernel List'" <ros-kernel at reactos.com>
Sent: Saturday, December 13, 2003 2:32 PM
Subject: [ros-kernel] Wine integration


> We have to make a choice very soon if we are going to 1) import the Wine
> headers and tools (libunicode,wpp,wrc) (a 12MB patch unfortunately) and
> import Wine DLLs or 2) submit patches to Wine to port the DLLs to w32api
> and then import them one by one as they are ported. 1) will give us
> something useful very quickly, but will also give us two sets of headers
> for some time. 2) will mean lots of work (my guess is several man months
> of work) and developers need to learn more about Wine developing than
> with 1).
>
> At this time, I consider the PR value of running applications like MS
> office higher than not duplicating code. IMHO ReactOS needs good PR and
> lots of it. So my vote is to go with 1) and integrate ReactOS and Wine
> headers in smaller steps (wether that means making Wine DLLs compile
> with w32api or making ReactOS compile with Wine headers).
>
> What are your thoughs on this?
>
> Casper
>
> _______________________________________________
> Ros-kernel mailing list
> Ros-kernel at reactos.com
> http://reactos.com/mailman/listinfo/ros-kernel
>