Hi, according to the pybind11 website the minimum supported compiler is VS 2015 Update 3. The python bindings now use pybind11, so for me this is another indicator 2015 is a good choice.
Regards Sebastian On 2018-11-26 23:56, Larry Gritz <[email protected]> wrote: > Crickets. > > I'm therefore going to assume that MSVS 2015 is the minimum. Not 2013, which > platform.h sure makes look like nobody could possibly have been relying on it. > > In light of that, I'm going to update the documentation to also say MSVS2015 > minimum. If somebody pipes up later that this is an unwise choice as we go > into calendar 2019, then we can always walk it back somehow. Better to add > support for an older compiler later, than try to remove support for a > compiler we advertised on release day to be supported. > > > > > On Nov 24, 2018, at 5:45 PM, Larry Gritz > > <[email protected](mailto:[email protected])> wrote: > > I *think*, based on https://msdn.microsoft.com/en-us/library/hh567368.aspx > > , that VS 2015 is the actual minimum version we need, since VS2013 doesn't > > appear to support constexpr, noexcept, and some other C++ features we > > definitely have in our code, and I haven't heard anybody complain. > > > > It also looks like src/include/OpenImageIO/platform.h (lines 92-109) will > > reject VS2013 (_MSC_VER >= 1900 is true only for VS2015+). > > > > So I believe that Visual Studio 2015 has, for all practical purposes, been > > our minimum for quite some time. But the "INSTALL.md" file says 2013 and I > > think that's an error. > > > > Further corroborating evidence: OSL's headers have the same test, and its > > INSTALL file is clear that MSVS 2015 is the minimum. I doubt very much that > > I would have intentionally had different minimum requirements for the OSL > > and OIIO versions I was developing at the same time. > > > > I think it's just a bug in OIIO's documentation, then, not correctly > > stating the de facto minimum of 2015. > > > > But I would really appreciate hearing from Windows users (a) confirm > > whether the tests in platform.h confirm that we have already been unable to > > build on on VS2013, and (b) that VS2015 is a reasonable minimum these days. > > Can somebody confirm or set me straight? > > > > > > > On Nov 24, 2018, at 3:26 PM, Larry Gritz > > > <[email protected](mailto:[email protected])> wrote: > > > To what degree is anybody still relying on MSVS 2013 and would object to > > > OIIO 2.0 bumping the minimum to 2015? > > > > > > > > > -- > > > Larry Gritz > > > [email protected](mailto:[email protected]) > > > > > > > > > > > > > > > _______________________________________________ > > > Oiio-dev mailing list > > > [email protected](mailto:[email protected]) > > > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org > > -- > > Larry Gritz > > [email protected](mailto:[email protected]) > > > > > > > > > > > > > > _______________________________________________ > > Oiio-dev mailing list > > [email protected](mailto:[email protected]) > > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org > -- > Larry Gritz > [email protected](mailto:[email protected]) > > > > > _______________________________________________ Oiio-dev mailing list > [email protected] > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org Sebastian Elsner - Head of Development - RISE t: +49 711 97469570 e: [email protected] w: www.risefx.com RISE FX GmbH Büchsenstraße 20, 70174 Stuttgart Schlesische Straße 28, 10997 Berlin Ehrenstraße 13, 50672 Köln Geschäftsführer: Sven Pannicke, Robert Pinnow Handelsregister Berlin HRB 106667 B
_______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
