No, it's not supposed to require OpenEXR 2.x, and if it doesn't build against OpenEXR 1.x, I consider that a bug.
In fact, this bug was fixed in 1.3.11. On Jan 20, 2014, at 3:20 AM, Matteo F. Vescovi <[email protected]> wrote: > Hi! > > On Mon, Jan 06, 2014 at 12:09:13PM -0800, Larry Gritz wrote: >> I've tagged Release-1.3.10. It's a bug-fix release with the following >> release notes: >> >> >> Release 1.3.10 (2 Jan 2013 -- compared to 1.3.9) >> ------------------------------------------------ >> * OpenEXR fix: multi-part EXR (2.0) didn't write the required "name" >> attribute for each part. > > So now OIIO 1.3.x requires OpenEXR >= 2.x to work? In fact, actually all > my attempts to build 1.3.x using OpenEXR 1.6.x failed. The real problem > here is that in Debian we don't have OpenEXR 2.x and OIIO won't build > anymore. Any chance to have a backport for now? > I started taking a look at OpenEXR in Debian to upgrade it to 2.x but > it ain't that easy. > > Hope you could help here somehow. > > Thanks in advance. > > > -- > Matteo F. Vescovi > Debian Maintainer > GnuPG KeyID: 0x83B2CF7A -- Larry Gritz [email protected] _______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
