On 2010-12-18 20:15+0100 Werner Smekal wrote: >> I made an attempt to run comprehensive_test.sh on my Windows system, >> via win-bash, but it requires basic external programs like dirname and >> basename that are not present on the average Windows machine. Using >> msys instead might be an option, but I noticed that CMake on Windows >> does not like it when there is a Bourne-shell present in the path. > > Yes, that's a known issue - cmake doesn't want sh.exe in the path, if there > is, it wants to use the msys makefiles generator. MSys is also far from > complete, since this is just the minimum environment to run the autoconf > tools. I would stay away from msys and stick with win-bash. The missing tools > (dirname, basename, ...) get from http://gnuwin32.sourceforge.net/ - the > shellutils package provides these tools. The cool thing about GnuWin32 is, > that these tools work also in standard Windows CLI (without > bash/msys/whatever). Actually I use these tools to improve my Windows CLI - > this works quite well.
Hi Werner: I have changed the subject line to something more appropriate for this thread. I think we will be able to give our Windows testers the choice of either MSYS-bash or win-bash (if that works for all Plplot tests which I have my doubts about, see below) and either gnuwin32 or MSYS. Arjen and I have just proved modern MSYS is complete enough to run all PLplot tests. For example, MSYS does include dirname and basename. I assume from what you have said that gnuwin32 (except for bash where you must use either MSYS-bash or win-bash for PLplot tests) is also complete enough to run the PLplot tests. I suspect the negative feelings you have expressed above about MSYS were established by your extensive experience with older versions of MSYS. Modern MSYS can be downloaded automatically with MinGW in ~5 minutes following the instructions in http://www.miscdebris.net/plplot_wiki/index.php?title=Install_MinGW/MSYS. Also as Arjen and I have recently discovered for Microsoft and wine versions of Windows, comprehensive_test.sh works well now with modern MSYS using the "MSYS Makefiles" generator. And I am about to generalize scripts/MinGW_MSYS_comprehensive_test.sh so that if the user prefers the "MinGW Makefiles" generator they can use it with the appropriate path manipulations to momentarily drop MSYS for the cmake invocation. That manipulation is possible with modern MSYS because the automatic installer keeps the MinGW and MSYS locations separate from each other. (Microsoft Windows users will have to test that "MinGW Makefiles" case for me when MinGW_MSYS_comprehensive_test.sh is generalized. Unlike the "MSYS Makefiles" case, I currently cannot test the "MinGW Makefiles" case on wine because certain CMake target dependencies are silently dropped by mingw32-make. mingw32-make uses many more native Windows features than the MSYS version of make, and therefore I assume this issue with mingw32-make on wine is due to some bug in wine's ability to mimic some Windows component used by mingw32-make which will be solved for some future version of wine.) MSYS-bash is easy to install now, and it has many modern bash features that win-bash doesn't have because win-bash development stopped many years ago. We did get win-bash to work for the limited "ctest" testing environment years ago, but I know the complete testing environment (e.g., including the pkg-config version of the build system for the installed examples) has many modern bash constructs (arrays, for example) which I doubt very much will work for win-bash now. And the situation is only going to get worse as more modern bash constructs creep into our PLplot test environment. Finally, you have expressed a legitimate concern that you prefer the tools you get with GnuWin32 to the (modern) MSYS ones. That should be fine, because all you have to do to assure you are using the GnuWin32 versions is to place the GnuWin32 location higher on the PATH than the MSYS location where MSYS-bash resides. In fact, for the planned change to scripts/MinGW_MSYS_comprehensive_test.sh, the MSYS location will automatically be put last in the PATH. We could also have an option to drop MSYS in the PATH altogether for those still wanting to try win-bash, but I don't think that version of bash will work for comprehensive PLplot testing for the reasons indicated above. Once I am ready, I hope you do test scripts/MinGW_MSYS_comprehensive_test.sh for the "MinGW Makefiles" case to be sure it works without issues for the combination of GnuWin32 tools (higher than MSYS on the PATH by design of MinGW_MSYS_comprehensive_test.sh) and MSYS-bash (or even win-bash if that actually works for comprehensive testing). 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 __________________________ ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
