Some of the WINE programs (for example, notepad) use resources for languages that arent present in the MingW headers, the Windows SDK or the visual C++ 6 header files (like LANG_WALON). Where did these definitions come from? Does windows actually use these definitions somehow? (Given that WINE is supposed to be a clone of the windows API, defining and using things that windows itself doesnt provide doesnt make sense)
IANACWD (I Am Not A Core Wine Developer) but I would think that being able to compile the standard Wine programs and some of the non-core dlls under MingW with w32api would be a usefull test.
Being able to replace e.g. comctl32.dll from MS with the wine version and seeing what breaks would be a good way to track down bugs (IMHO) Same for Wine programs (like notepad), being able to build & use em on win32 would help with bug tracking. (i.e. is this bug in WINE or in the app)
Being able to replace e.g. comctl32.dll from MS with the wine version and seeing what breaks would be a good way to track down bugs (IMHO) Same for Wine programs (like notepad), being able to build & use em on win32 would help with bug tracking. (i.e. is this bug in WINE or in the app)
I work on this for the ReactOS project. It is a very slow process cleaning up WINE to use the w32api package.
1. You will need MSYS+Mingw 2. ./configure --disable-win16 3. make tools 4. make 5. remove a header from wine/include and try to build the dll/program you are cleaning up.this will let you use the mingw header. 6. Fix WINE/w32api if something is broken
most dlls/programs build now with the WINE headers but for ReactOS we have to fix w32api.
Thanks Steven
__________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com
On July 19, 2003 02:33 am, Jonathan Wilson wrote:
Being able to replace e.g. comctl32.dll from MS with the wine version and seeing what breaks would be a good way to track down bugs (IMHO) Same for Wine programs (like notepad), being able to build & use em on win32 would help with bug tracking. (i.e. is this bug in WINE or in the app)
Yes, having as much of our code compilable under Windows is important, so we should stick to the standard Win32 API as much as possible. This is not always easy, so people make shortcuts at times. These need fixing.