[ros-kernel] Proposed ReactOS headers and code sharing policy

Jonathan Wilson jonwil at tpgi.com.au
Sun Oct 19 09:25:37 CEST 2003


Here is how I think the proposal should proceed:
1.we move the ReactOS internal headers out of the way
2.we import current MingW-Runtime and w32api CVS into our tree or whatever
3.we build
4.we fix errors untill stuff builds again
5.also, we get permission from the WINE team (from whoever we need 
permission from) to use those bits of the WINE headers that MingW doesnt 
have in the new MingW (e.g. some of the directx stuff)
6.we work towards having as much of the dlls as possible usable on real windows
and 7.we look for places where we are duplicating code with WINE (e.g. 
msvcrt/crtdll)

Ideally it would be good if the WINE team was to switch to this new 
"perfect" header set also at some point down the line.

Personally, I think we should have an extra set of headers for things that are:
A.exported by windows (either user mode or kernel mode)
B.not documented by MS (and not in the Platform SDK)
and C.documented by someone else




More information about the Ros-kernel mailing list