[ros-kernel] RE: Bug tracking organization

[Steven E. <Ste...@ya...>]

> Hi Steven,
> Are these changes and patches going to replace the wine 
> package in the ROS CVS tree? If so, will it build with ROS? 
> I'm not following the mail lists as I should.
> 
> Good work! I'll be back on the project soon as I finish two 
> more work projects. Thanks, James
> 

Hola James,
Yes, hopefully In a few weeks I will bring the ReactOS wine tree back 
up to sync with the winehq tree. I still have about 4 or 5 patches I
need
To submit to the wine tree. I will need your and Capser's help 
If you have time. The there are only a few things stoping us from being 
Able to do a easy import of the wine sources at anytime.

1. Makefiles -
ReactOS can still use its own makefiles for its fork but I would like to
see a shell script 
That auto parses the Makefile.in for our fork and generates our
makefile.ros for us.

2. Def files - 
Winebuild can build these now. It works under mingw, so we need to fix
our build system
To autogenerate the *.defs from the wine *.spec

3. Resources - This will need to be fixed in the the wine makefile
structure for mingw
And the reactos build system. We do not need to fork the wine resources
as windress can
Build a .coff out of the wrc compiled resources. So the build system
will need to be 
fixed like this

(1)Build the objects.
(2)Run wrc on the wine resources to get the compiled *.res
(3)Run windress to make a *.coff out of the res.
(4) Link the dll/program

4. Wine Debugging -
I have no clue here as am still to new to the programming gig. Our ntdll
will need to be 
updated for the need debugging interfaces in wine.

I have about 100 other little things I would like to see, but on the
ReactOS side this should
Do it for a while.

Thanks
Steven


"Every revolution was once a thought in one man's mind"
- Ralph Waldo Emerson