How do I run a wine perl regression test in Windows?
I thought the entire point was to make it so you don't need a c-compiler, yet I can't seem to get the tests to run without the winetest application (which I've been unable to build on windows so far). Is it planned that this executable be distributed with wine, or am I missing something else?
Ideally, I'd like to be able to get just the tests and required apps through cvs (or even a .zip file), and run them. If this is possible today, it isn't obvious (to me) how to do it.
Sorry if this is documented somewhere, but I checked Francois' presentation, and the huge thread in January, and didn't find anything about it. If you want to convince people to help write tests, it'd sure be nice if it was easy to find information about how to do it :)
.Geoff
----------------------------------------------------- Protect yourself from spam, use http://sneakemail.com
On 23 Mar 2002, Geoffrey Hausheer wrote:
How do I run a wine perl regression test in Windows?
Well, that's part of the unfinished items. Currently you have to: * install Perl on Windows The best seems to be to get Perl from source and compile it, e.g. with Visual C++. * get the whole Wine tree to Windows * tweak programs/winetest/Makefile.win32 to adapt to the directory where you have perl installed. Typically just replace PERLDIR = c:\perl\5.6.0\lib\MSWin32-x86\CORE XSUBPPDIR = c:\perl\5.6.0\lib\ExtUtils with PERLDIR = c:\perl\5.6.1\lib\MSWin32-x86\CORE XSUBPPDIR = c:\perl\5.6.1\lib\ExtUtils * run tests manually by invoking programs/winetest/runtests with the right options.
I thought the entire point was to make it so you don't need a c-compiler, yet I can't seem to get the tests to run without the winetest application (which I've been unable to build on windows so far). Is it planned that this executable be distributed with wine, or am I missing something else?
Is it planned, yes. Is it done? No, not yet :-(
Ideally, I'd like to be able to get just the tests and required apps through cvs (or even a .zip file), and run them. If this is possible today, it isn't obvious (to me) how to do it.
Yes, that's the plan: regularly generate a zip file to put on WineHQ, so that people can just grab the zip file and run some batch script to invoke all the tests.
Perl tests aside, I have started working on a perl script that would generate Makefiles suitable for running the C tests on Windows using Visual C++. But it's not finished yet and I had to stop working on it for a while. I attached it to this email so that someone can pick it up. Please let me know if you do.
Sorry if this is documented somewhere, but I checked Francois' presentation, and the huge thread in January, and didn't find anything about it.
That's another item: my presentation should be converted and integrated into the Wine Developper's Guide. That's the right place for such documentation.
-- Francois Gouget fgouget@free.fr http://fgouget.free.fr/ The greatest programming project of all took six days; on the seventh day the programmer rested. We've been trying to debug the *&^%$#@ thing ever since. Moral: design before you implement.