On 2014-09-04 17:14+0100 Phil Rosenberg wrote: > Hi everyone > I just wondered if anyone has tried the test scripts on windows? > > Making the changes to get rid of exit calls and improve memory management is > rather intrusive so I would like to do some pretty thorough testing before I > push anything. > > I have access to bash through Cygwin, but I couldn't immediately see any > readme associated with the test scripts so I thought I would try and get some > advice before starting.
I am the author of scripts/comprehensive_test.sh, and to answer your question, it works fine for me on both Linux and MinGW/MSYS. Of course, my MinGW/MSYS tests are still quite limited because of the lack of libraries for MSYS (even though I partially addressed that issue with epa_build). As far as I know there is no fundamental reason why that script should not work for the Cygwin platform, but since you would be the first to try it on that platform, some changes might be required to get it to work. To get help for that script, simply run scripts/comprehensive_test.sh --help I suggest you use lots of those many documented options to keep the test small to start. For example, --do_shared yes --do_nondynamic no --do_static no implies only one (shared + dynamic devices) of our three major configurations are tested; --do_test_noninteractive yes --do_test_interactive no implies that only noninteractive tests will be done; --do_test_build_tree yes --do_test_install_tree no --do_test_traditional_install_tree no implies only tests in the build tree will be run; and --do_ctest no means that ctest will not be run in the build tree. If your current set of tests is simply to do build testing in the build tree, then the above combination of options is equivalent to that with "make test_interactive" added to give you run-time testing using the noninteractive devices. If you are having trouble getting even the above limited testing to work on Cygwin, then I suggest you limit the tests even further to give you the simplest possible debug case. For example --cmake_added_options "-DDEFAULT_NO_BINDINGS=ON -DDEFAULT_NO_DEVICES=ON -DPLD_ps=ON" means none of the bindings libraries and none of the devices (other than ps and psc) will be built or tested in any context of the comprehensive test. My ultimate goal with comprehensive_tests.sh is to get it to work on all platforms where bash(.exe) is on the PATH so I am most interested in what you find for the Cygwin platform case, and I would be happy to help you with any problems you encounter on that platform. Once that works (and with all the above initial constraints on the scope of the comprehensive testing removed), then it should not be that large a step (I think) to get it to also work for MSVC/nmake on Windows so long as bash.exe on the PATH did not interfere with MSVC/nmake. However, if you are thinking of trying that MSVC/nmake case first, I would be happy to help with that as well. 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); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); 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 __________________________ ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ _______________________________________________ Plplot-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/plplot-devel
