RE: [ros-kernel] Prototype conflicts in current wine port

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

> With my solution the trees won't need to differ. comdlg32 
> will simply use libwine_unicode on both platforms; and you 
> will need libwine_unicode on ReactOS anyway so this shouldn't 
> be a limitation.

This is true we will need libwine_unicode.dll to be able to use
Wrc to compile the resources before we feed them to windress.
 
> It could be possible later on to have an optimized version of 
> libwine_unicode on ReactOS that uses the msvcrt functions, 
> but that's probably not very high priority right now...

No its not. The high priority for us is the gcc self-hosing and 
Getting winhello working.

Thanks
Steven

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