Hola and Thanks for everything so far in getting the Mingw port rolling.
Doing my work on getting shlwapi.dll built I noticed the missing imports from user32 wvsnprintfA@16 and wvsnprintfW@16 in libuser32.a. I was going to submit a patch to the mingw developers for the Win32api package that updates the libuser32.a and I am still planning on doing that but I think a more self-contained solution would be better.
In the ReactOS tree we have a "make implib" rule to generate all of the import Libs for our shared libs. This way we are not dependant on the mingw win32api. I think the wine tree needs to do something similer. Once this is done we can go ahead and build the import libs for ntdll, msvcrt and User32 that are needed for the wine dlls.
The command line is something like this dlltool --as=as --dllname user32.dll --def user32.spec.def --output-lib libuser32.a
The only real problem isnt really a problem but we just wouldn't catch it in the build processes. If WINES libuser32.a exported a non-win32 function that we shouldn't Use anyway and another dll imported that function (see comctl32) like GetSysColorPen (see wine/windows/syscolor.c line 388) The build would still work and we wouldn't catch it untill someone tries to use comctl32.dll without wines user32.dll.
I still think the change would be for the better and request your comments.
Thanks Steven
"Every revolution was once a thought in one man's mind" - Ralph Waldo Emerson