For reference, our current master and 2.0.x releases use a minimum of CMake 3.2, so people are certainly not using a stock 2.8, which would have been rejected by our build system for quite some time now.
And like I said, the soon-to-be-released OpenEXR 2.4 will have a 3.12 requirement as well, so anyone who wants to stay current on OpenEXR will have the same requirement from them. On the plus side, one thing that's extra nice about 3.12 is that the default behavior of all the built-in find_package(Package) functionality is to *automatically* use any -DPackage_ROOT=path or environment variable Package_ROOT=path to give hints about overrides for finding the package in question. Which means that we can rip a lot of boilerplate and custom options out of both our CMakeLists.txt and our wrapper Makefile, but still have the same functionality of overrides, including now having them automatically for even the dependencies where we never got around to adding special options to override the search for those packages. > On Sep 5, 2019, at 6:26 PM, Richard Shaw <hobbes1...@gmail.com> wrote: > > On Thu, Sep 5, 2019 at 6:24 PM Larry Gritz <l...@larrygritz.com > <mailto:l...@larrygritz.com>> wrote: > Is anybody under hard constraints on what cmake versions they can use? > > In particular, how badly would people get bent out of shape if moving forward > we required CMake >= 3.12? > > Straight EL 7 is still on 2.8 but via Fedora EPEL (all I care about) I have > 3.13.5 available. > > I'm not sure about RHEL 8 since I won't have easy access to CentOS until they > release. > > Thanks, > Richard > _______________________________________________ > Oiio-dev mailing list > Oiio-dev@lists.openimageio.org > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org -- Larry Gritz l...@larrygritz.com
_______________________________________________ Oiio-dev mailing list Oiio-dev@lists.openimageio.org http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
