Hi,
Indeed silence means it's ok to move to VFX platform 2015. I didn't
reply having nothing else to do than 'Ok'.
I agree also on raising the minimum boost version, at least to 1.54. (it
fixes some issues we stumbled on using versions >1.49 and <1.54 with
shared pointers)
On 12/22/2014 09:47 PM, Larry Gritz wrote:
CC'ing to osl-dev as well, on the off-chance that somebody important is reading
there but not on oiio-dev. The two projects will likely take this step
simultaneously, after they both have had their next release branch.
I did not see a single reply about this. May I assume that after OIIO 1.5 is
branched for release, that everybody is ok for future development in master to
raise the minimum compiler feature requirements to the equivalent of gcc 4.8.1?
As far as I know, there's nothing in gcc 4.8.1 that isn't in clang 3.3 and
MSVC++ 11.0 (aka Visual Studio 2012). Also ok?
None of these are exactly cutting edge (alas, we are not yet even requiring
full C++11 compliance, whereas the very latest revs of the major compilers can
handle C++14), and this is in line with the VES guidelines that Autodesk, SESI,
and Foundry have pledged to follow for their 2015 product releases.
Also I am considering raising the floor on boost. What's reasonable? VES says
1.55, but I don't know if that's realistic. At this very moment, I do not have
anything in particular in mind that requires anything new, but it would be nice
to remove some #if's that preserve compatibility with pre-1.50 boost versions.
Once again, none of this will affect the requirements of the as-yet-unreleased
OIIO 1.5 or OSL 1.6 or any patches thereto. We're only talking about the
hypothetical future OIIO 1.6 / OSL 1.7 and beyond.
This is also pending my own facility being ready for such a switch. I may yet
be the gating factor here, but even when I'm ready, I don't want to throw the
switch if it's going to leave somebody important out in the cold.
-- lg
On Nov 27, 2014, at 3:58 PM, Larry Gritz <[email protected]> wrote:
We are aiming to branch and release OIIO 1.5 before the end of the year, with
the same old language and compiler requirements we have always had. We have
strived thus far to continue being compatible with gcc 4.1 (and, I think, MSVC
9?, something fairly old).
In case you are not aware of it, http://www.vfxplatform.com/
On Linux, the major VFX vendors and studios are all planning to upgrade their
gcc floor from 4.1 to 4.8 for anything released in 2015 (though, alas, not full
C++11 until possibly the next year).
I've been coveting a lot of the new C++ features -- auto, move semantics,
initializer lists, lambdas, range-based 'for', and so on. This page has a handy
chart of compiler versions versus new C++ features:
http://wiki.apache.org/stdcxx/C%2B%2B0xCompilerSupport
It looks to me like a rather nice batch of features allowed by gcc 4.8 should also be
supported by clang >= 3.1 and MSVC >= 11.0 (I think that's Visual Studio 2012).
So, the particular question to contemplate over the next few weeks:
* For new development in 2015 and beyond (OIIO >= 1.6), is there anybody who would still
have a reasonable requirement for gcc < 4.8, MSVC < 11.0, or clang < 3.1? Keep in
mind that we would continue to have available and support OIIO 1.5 that only needs
gcc4.1/msvc9.0, and as well that being incompatible with gcc >= 4.8 will probably also make
you incompatible with next year's Maya, Houdini, Nuke, and so on.
My current inclination is to wrap up OIIO 1.5 release with the current C++ feature set
we've been using, but then starting in January allow new development to use some
additional C++ features. Exactly which features is TBD, and will depend on what the new
"floor" is that we decide for the compiler versions on the major platforms.
Suggestions and feedback appreciated.
--
Larry Gritz
[email protected]
_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
--
Larry Gritz
[email protected]
_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
