Alexandre Julliard wrote:
"Dmitry Timoshkov" dmitry@codeweavers.com writes:
"John Klehm" xixsimplicityxix@gmail.com wrote:
The problem is that it is a mingw issue but they don't want any patches from wines win32 api in their mingw w32api. They believe that looking at the actual ms header files taints our headers legally speaking. Stefan, hans, and PaulM maintain a rather large set of patches against w32api. [1]
So its a constant catchup game from when wines headers get new additions until someone sends paulm a patch updating the mingw w32api.
Then perhaps we (Alexandre) should reconsider the stance about using Wine headers and import libraries in preference to mingw ones.
Agreed, the idea of using w32api is that we want to help improve mingw by finding problems in their headers and libraries, but if they are not going to accept our patches anyway, then there's clearly no point in continuing to make our life harder by using their stuff.
And can't we just start creating the winetest executable at winehq somewhere?