On 2016-02-07 12:29-0800 Greg Jung wrote: > The platform where bugs are appearing is MSVC because of the new OS.
Hi Greg: There were clearly some MSVC bugs in immature versions of both 3.3 and 3.4 so that is why I avoid such immature versions when setting the minimum version. So the current choices are just 3.3.2 or 3.4.3. My further impression from following both the cmake and cmake-devel lists is that MSVC works better for 3.4.3 than it does for 3.3.2, i.e., over time the MSVC support is greatly improving, but I obviously don't have any hands-on MSVC experience in that regard. > I'm pretty sure 3.4.3, without modifications, will break in plplot > comprehensive > on my 'puter when it picks up a windows' pythonlib from the registry. I am virtually positive there is a way around the issue of finding your desired Python version with vanilla CMake even on Windows platforms. For example, $install_prefix/share/cmake-3.4/Modules/FindPythonLibs.cmake says: # If you'd like to specify the installation of Python to use, you should # modify the following cache variables: # # :: # # PYTHON_LIBRARY - path to the python library # PYTHON_INCLUDE_DIR - path to where Python.h is found i.e., use the cmake command-line options -DPYTHON_LIBRARY:PATH=whatever -DPYTHON_INCLUDE_DIR:PATH=whichever So I would strongly advise you to use that solution as opposed to hacking CMake itself to make your life with regard to cmake upgrades much easier. > > I have already given 3.4.3 a pretty >> >> good thrashing on Linux so I expect there is an excellent chance it >> will be reliable for all your various platform needs as well. > > Of course, Linux is the worst test because it is most likely to be > compliant, > the most tested and consistent. The minority case uses are where issues > are more likely to arise. That is a very good point. And I am also concerned with Mac OS X users as well who will be affected by this change. So I now realize I got ahead of myself and before doing the bump I should have encouraged all here to test 3.4.3 on platforms of interest to them. Thus, I am currently leaning toward reverting this change for say the next 3 months while users do such testing. I would also like to hear from other MSVC users and also Mac OS X users about what ideal schedule they would like to see for bumping the minimum version, e.g., once each CMake minor version matures (i.e., cmake-3.4.3, cmake-3.5.last, cmake-3.6.last, ...) or once every other CMake minor version matures (cmake-3.4.3, cmake-3.6.last, cmake-3.8.last, ...)? 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 __________________________ ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
