To Arjen and Chris: @Arjen:
I saw your remark that you were going to write off the Cygwin platform for case (4) testing, but please hold off on that decision until Chris clarifies what he said below: On 2017-05-05 08:24-0400 Chris Marshall wrote: > cygwin doesn't handle install directories with whitespace fully or at all. @Chris: To clarify what you said, are you concerned that basic functionality (compilers, CMake, C, library, Unix tools like bash) just won't work at all on Cygwin if a "spaced" install prefix is used? Or are you concerned that some libaries which are soft dependencies of PLplot but which are not fundamental to Cygwin's basic functionality won't work for this "spaced" case? If the latter, I agree there are likely to be such cases (since free software has historically struggled with spaces in full pathnames just like PLplot is doing now), but that does not preclude us testing for case (4) issues for PLplot on Cygwin. @ Both: The argument is if a PLplot build with all bindings and devices that depend on external libraries disabled is a success for this "spaced" install prefix case, then that proves the basic functionality of Cygwin works for this case. And if you then follow up by removing all those constraints from the PLplot build, then you will likely encounter (as I stated above) some problems for certain PLplot components. However, for these cases a quick visual check of "make VERBOSE=1" results should tell you whether the command that is failing has been set up properly by our build system so that the blanks are quoted or escaped properly. And if we fix all such issues (or there are none) and the command still fails, then we will have to blacklist that component of PLplot (i.e., disable it) for "spaced" install prefixes until the external package sorts out its own problems for that scenario. Note, this argument is a general one so it also applies to both the MinGW-w64/MSYS2 and epa_build platforms. If the platform fundamentals work for a "spaced" installation prefix (which is true almost by definition for at least the epa_build case) then sorting out whether the trouble for a given component of PLplot is due to an issue with our build system or the external software component for the platform should be completely straightforward. 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 __________________________ ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
