On Tue, 26 Aug 2003, Ferenc Wagner wrote:
Francois Gouget fgouget@free.fr writes:
You suggested a script to generate a zip file automatically. I have a couple of trivial scripts that should do 90% of the job.
- zipmsvctests
Exactly what I envisioned. What do you think about putting it into the Wine CVS tree so that anyone compiling the tests could use it? Into tools/ for example?
I would not mind but see below.
- runtests.bat
Maybe we could do a bit more here, like redirecting the output into a file and echoing back a counter between the tests as a kind of "progress bar".
Possibly but remember that batch files are erally restricted in what they can do. The batch file also has to run on both Win9x and NT*.
I could probably write a Perl script to generate the above scripts, but I am not sure if it is wise to require Perl from the good soul trying to compile the tests for us. So maybe we are better including the results (as well) in the tree.
I think that's the way to go. Anyone wishing to compile the tests with MSVC already needs to use perl scripts to generate the Visual Studio project files. These scripts could probably easily be modified to generate the above batch files too. That would be much more maintainable than putting hard-coded scripts into Wine.
Then we would run the script on a Unix machine and upload them some place so that Windows users can get them and build without installing perl.
All we need is to FIX the BUGS and then it will all be trivial to manage.
Golden words!
Yep, and it should not even be too hard since it's only the bugs in the tests that we need to fix in this case.