1.7.0 was indeed the first version to ship with that header, although it was in the CVS for some time before 1.7 was released.
Weta back-ported support for the attribute into our 1.6 build, as did quite a few others. An autoconf type mechanism might be the most robust way of detecting support for that attribute -------- Original message -------- Subject: Re: [Openexr-devel] Unpacking the multiView attribute? From: Stewart Dickson <sdick...@wolfram.com> To: Paul Miller <p...@fxtech.com> CC: openexr-devel@nongnu.org Nope, In openexr-1.7.0/IlmImf there exists: ImfStringVectorAttribute.h In openexr-1.6.1/IlmImf no such beast. Which brings up my next question. Is there a way to switch #if defined(OPENEXR_VERSION > 1.6.1) To turn off reference to StringVectorAttribute when building against openexr-1.6.1 version of the code? Thanks, -Stewart ----- Original Message ----- From: "Paul Miller" <p...@fxtech.com> To: "Stewart Dickson" <sdick...@wolfram.com> Cc: openexr-devel@nongnu.org Sent: Friday, February 3, 2012 3:05:20 PM Subject: Re: [Openexr-devel] Unpacking the multiView attribute? On 2/3/2012 2:22 PM, Stewart Dickson wrote: > Thanks, Paul, > > Is this in OpenEXR version 1.7.0? > > In openexr-1.6.1, I get: > error: ISO C++ forbids declaration of ‘StringVectorAttribute’ with no type It's probably in the Imf namespace. I have a using namespace Imf; using namespace Imath; at the top of my code. I'm pretty sure it was in 1.6. _______________________________________________ Openexr-devel mailing list Openexr-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/openexr-devel
_______________________________________________ Openexr-devel mailing list Openexr-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/openexr-devel
