interesting ... let me know what comes of that. In the mean-time I'll
take a look at the so versioning on 1.7.0.

Piotr


On Wed, Jul 20, 2011 at 3:13 PM, Stephen Parker
<[email protected]> wrote:
> I replied to Larry off-list (accidentally), but more than likely my problem
> relates to a host application statically linking to an older OpenEXR
> library. It's more of a hunch though and I thought I'd ask if anyone was
> successfully using 1.7 because my plug-in basically asserts in
> exrinput.cpp:query_channels that it can't figure out the channel type.
> Please don't bother with this until I have more details... but if you are
> having success with OpenEXR 1.7, I'd love to scratch that off my list as a
> possible candidate.
> thanks
>
>
>
> ________________________________
> From: Larry Gritz <[email protected]>
> To: OpenImageIO developers <[email protected]>
> Cc: Stephen Parker <[email protected]>
> Sent: Wednesday, July 20, 2011 1:31 PM
> Subject: Re: [Oiio-dev] OpenEXR 1.7
>
> I've been using 1.6 on my own machines as well.  If 1.7 is a problem, please
> let us know ASAP.
>
> Also, I've been involved with the development of OpenEXR 2.0, so we hope to
> have OIIO support for that in time for its release.
>
>     -- lg
>
>
> On Jul 20, 2011, at 11:15 AM, Jeremy Selan wrote:
>
>> At Imageworks, our current system-level installation is exr 1.6 based.
>>
>> -- Jeremy
>>
>> On Wed, Jul 20, 2011 at 11:07 AM, Stephen Parker
>> <[email protected]> wrote:
>>> Out of curiousity, are most people building OIIO against 1.6.1 or 1.7 of
>>> the
>>> OpenEXR library? I realize no one can answer that definitively, but I was
>>> curious what the devs are using.
>
> --
> 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