Unfortunately there are no pre-compiled binaries yet. However if send an email to the Wine development list you can probably get someone to send them to you, and maybe motivate some kind soul to put in place a mechanism for publishing such binaries on a regular basis.
get the Wine sources
Run msvcmaker to generate Visual C++ project files for the tests. 'msvcmaker' is a perl script so you may be able to run it on Windows.
$ ./tools/winapi/msvcmaker --no-wine |
If the previous steps were done on your Linux development machine, make the Wine sources accessible to the Windows machine on which you are going to compile them. Typically you would do this using Samba but copying them altogether would work too.
On the Windows machine, open the winetest.dsw workspace. This will load each test's project. For each test there are two configurations: one compiles the test with the Wine headers, and the other uses the Visual C++ headers. Some tests will compile fine with the former, but most will require the latter.
Open the Build+Batch build... menu and select the tests and build configurations you want to build. Then click on Build.
To run a specific test from Visual C++, go to Project+Settings.... There select that test's project and build configuration and go to the Debug tab. There type the name of the specific test to run (e.g. 'thread') in the Program arguments field. Validate your change by clicking on Ok and start the test by clicking the red exclamation mark (or hitting 'F5' or any other usual method).
You can also run the tests from the command line. You will find them in either Output\Win32_Wine_Headers or Output\Win32_MSVC_Headers depending on the build method. So to run the kernel 'path' tests you would do:
C:\>cd dlls\kernel\tests\Output\Win32_MSVC_Headers C:\dlls\kernel\tests\Output\Win32_MSVC_Headers>kernel32_test thread |
This needs to be documented. The best may be to ask on the Wine development mailing list and update this documentation with the result of your inquiry.
Here is how to generate Windows executables for the tests straight from the comfort of Linux.
First you need to get the MinGW cross-compiler. On Debian all you need to do is type apt-get install mingw32.
If you had already run configure, then delete config.cache and re-run configure. You can then run make crosstest. To sum up:
$ rm config.cache $ ./configure $ make crosstest |
If you get an error when compiling winsock.h then you probably need to apply the following patch: http://www.winehq.com/hypermail/wine-patches/2002/12/0157.html