Hi Phil and Arjen: I got a response to the question in the subject line on the CMake list which I share here in edited form.
--------------------------------------------------------------- On 2014-10-31 08:14-0000 Mueller-Roemer, Johannes Sebastian wrote: > I have only used MinGW-w64 for years and MinGW Makefiles works just fine. The > main difference between MinGW-w64 and the original MinGW is that it is far > more up to date. > Binary packages can be found here: > http://mingw-w64.sourceforge.net/download.php > I generally recommend using the mingw-builds binary packages From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca] Sent: Friday, October 31, 2014 11:19 What is the name of the make command you use, and is it part of the mingw-builds binary packages that you recommend? Date: Fri, 31 Oct 2014 10:47:45 +0000 From: "Mueller-Roemer, Johannes Sebastian" mingw32-make, and yes it's included. --------------------------------------------------------------- So this should exactly answer how to use MinGW-w64 alone (no MSYS or MSYS2), and I am pretty sure (because of similarities with Cygwin) my suggestion (starting with the MSYS2 install procedure documented at a link you can find at http://sourceforge.net/p/msys2/wiki/Home/) about how to use the combination of MinGW-w64 and MSYS2 with the "Unix Makefiles" generator is correct as well. These two MinGW-w64 platforms are relevant to us as test platforms because obviously some PLplot users such as Greg are beginning to use MinGW-w64. MSYS2 and Cygwin are not accessible to me at all on Wine because of well-know Wine bugs that don't let the MSYS2 and Cygwin installers even complete. So I cannot directly help you with testing those two platforms. However, I have had success with MinGW alone and MinGW/MSYS in the past on Wine, and I will likely try MinGW-w64 alone as well on Wine to see how far I get using the binary package recommended by Johannes. So that leaves 2 gcc-related Windows platforms and maybe a third where I can help with testing later in this release cycle especially if either of you guys finds issues with any of those three. And, of course, I would be willing to help (at one remove) if either of you discovers build-system issues with Cygwin or MinGW-w64/MSYS2. Test coverage of the 5 different gcc-related Windows platforms may seem like a big burden to you guys, but I believe automated testing with scripts/comprehensive_test.sh (which is what I have used so far with complete success on MinGW/MSYS) is the answer here to reduce the testing burden to a minimum. 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 __________________________ ------------------------------------------------------------------------------ _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
