Am 28.08.2013 02:40, schrieb Larry Gritz:
> I won't hold you to this. And I'm not planning any immediate changes.  But 
> thinking about where we are going with toolchain dependencies, coding 
> standards, and how conservative we need to be about newer C++ features...
>
> Think ahead to where you or your facility will likely be in, say, January 
> 2014.
>
> * What C++ compiler and version do you think will be the oldest (i.e., least 
> C++11-compliant) you'll need OIIO to support?

On Windows you are free to use every compiler version since you have to
compile all libraries yourself anyway. But this is only for open source
apps.  I am thinking more in a way of "host applications" I do not have
control over. For example OIIO is used by MtoA, MtoA must run in Maya,
and Maya is VS 2010. Nuke uses 2010, too. So we need to stick to those
compiler versions, because of big incompatibilities. On Linux Maya uses
4.1.3, which is pretty old I guess. The standard Python 2.6/2.7 again,
that  comes with the official installer is VS 2008 (as is Houdini for
example). Since we will be stuck with Py 2.6 for a while (I guess, since
there seems to be no urge in any software package to move to 3) 2008 is
the lowest for windows. I guess to use all the super new feature of
C++11 VS 2012 would be needed since older versions are not very compliant...
 Right now we are on Windows only, but that will change. We will be
going with a stock CentOS 6.x. So its 4.4 there?
> * What Boost version do you think will be the oldest you'll need OIIO to 
> support?

Don't care.

>
> * Can you think of any other dependencies (OpenEXR, etc.) that you are likely 
> to need support for any versions MORE THAN TWO YEARS OLD, i.e., dating from 
> 2011 or earlier?
AFAIK None.

>
> If you aren't comfortable answering on the mail list, a private email to me 
> is fine, and I will summarize results later.
>
> For simplicity, you need not reply if you are already using this year's 
> tools: GCC >= 4.8, MSVC >= 11 (VS 2012), Clang >= 3.3.
>
>
> --
> 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

Reply via email to