On 2009-01-19 08:52+0100 Arjen Markus wrote: > > It is a pity that I cannot use these testing scripts under plain Windows. > One addtional thing to do: create batch files that will do the same > thing (or at least approximate the shell scripts).
Hi Arjen: The current set of shell scripts for testing have had constant maintenance and improvement as long as I can remember. So I think taking a windows batch file approach to do the same thing would create a substantial maintenance issue that we should avoid if at all possible. So I suggest you try using win-bash instead. As far as I know (but I hope Werner comments further), that is completely supported by our build system. For example, that build system searches for bash in the following way (in plplot.cmake): find_program(SH_EXECUTABLE bash) find_program(SH_EXECUTABLE win-bash) That is, it first looks for bash, and if it cannot find it, it then searches for win-bash. The first lines of all our scripts use whatever that SH_EXECUTABLE turns out to be. So I suggest you install win-bash (following the instructions at http://win-bash.sourceforge.net/) and then run cmake with the -DBUILD_TEST=ON option. Also, check the cmake output to make sure there are now warning messages such as WARNING: bash shell not found, ctest will not work properly Once you have a cmake run without that warning, then run make (or nmake) then ctest --exclude-regex compare I am specifically requesting you try ctest without the compare test since that test runs test_diff.sh which in turn uses tail and diff executables where no windows substitutes have been configured (although presumably that could be arranged). N.B. I am making an educated guess that win-bash will get ctest working for you, based on what I see has been put into the build system by Werner. However, I obviously have not had any windows experience myself, and I am hoping Werner will join the discussion at this point and give some of his practical experience with win-bash and ctest. Note that all ctest does is run plplot-test.sh with various options (if you exclude the comparison test as above). That (and a run of test_diff.sh at the end) is exactly what happens at a fundamental level in the install tree as well. That means once you have ctest working for Windows, then the potential exists to get the install-tree tests to work as well on Windows. Of course, in the install tree you would have to find some windows equivalent of the Makefile that organizes all those plplot-test.sh runs with various options, but that is a much smaller maintenance issue then duplicating the detailed functionality of plplot-test.sh. Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); PLplot scientific plotting software package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
