As a matter of fact, we had OCIO v2 development tree all working in OIIO 2.2
and master... until this past weekend, when they moved some declarations around
between header files (deleting one header that we included), breaking our build
vs OCIOv2. I've already fixed it, but hadn't pushed out a 2.2 release. I will
double check everything and push an OIIO release tonight that addresses this
one thing.
-- lg
> On Jan 7, 2021, at 6:54 PM, Stephen Mackenzie <max...@gmail.com> wrote:
>
> Apologies if I missed a memo, just want to check on this, and it didn't seem
> like a github issue.
>
> Since OCIO-2 has an RC, I was hoping to get latest-gen OIIO-2's built against
> it for testing, but as soon as I advance OCIO-2 from it's master branch
> commit around 2020-06-09, OIIO-2's compile (any version I've tested between
> 2.1 and 2.2.10.0 today) breaks with fairly obvious nontrivial errors.
>
> Is there a dev branch testing support, or has this just not been hammered on
> yet by chance and my poor timing? (Or is it supposed to work and I'm just
> doing something horribly wrong...? Never can be sure.)
>
> Unfortunately, I can't honestly tell whether the potential github issue would
> fall under OIIO's camp or OCIO's, so a little clarity on that might be nice
> as well, just so I can file my request under the correct umbrella. (I won't
> bother pasting logs unless requested, as I'm guessing this not working isn't
> a surprise, but please correct me otherwise)
>
> Thanks!
>
> -Stephen
>
> _______________________________________________
> Oiio-dev mailing list
> Oiio-dev@lists.openimageio.org
> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
--
Larry Gritz
l...@larrygritz.com
_______________________________________________
Oiio-dev mailing list
Oiio-dev@lists.openimageio.org
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
