Also FYI, I've been made a co-maintainer of yaml-cpp for Fedora so
that should make things easier.

Thanks,
Richard

On Wed, Feb 1, 2012 at 11:14 AM, Jeremy Selan <jeremy...@...> wrote:

We're looking at 0.3.0  (which maintains the current yaml API).   I talked
to the developer, and the new API is a bit too in flux / untested to want to
jump to it in the short term.

I've got a branch of OCIO where I've been playing with 0.3.0:
https://github.com/jeremyselan/OpenColorIO/tree/yaml

I build my own yaml-cpp 0.3.0 packages tried your branch (it took me a
while to update my patch) but it now builds and pass the current tests
so that's promising.

Thanks,
Richard

On Wed, Feb 1, 2012 at 11:14 AM, Jeremy Selan <jeremy...@...> wrote:

We're looking at 0.3.0  (which maintains the current yaml API).   I talked
to the developer, and the new API is a bit too in flux / untested to want to
jump to it in the short term.

I've got a branch of OCIO where I've been playing with 0.3.0:
https://github.com/jeremyselan/OpenColorIO/tree/yaml

This will probably become a pull request once I get the appropriate unit
tests in, and work out an issue with regards to null token.

The good part is that the ocio yaml patch file goes away (other than the
enabling of -fPIC)

Thanks for the quick reply! I just submitted a bug[1] to request the
Fedora maintainer update to 0.3.0. I'll make sure that -fPIC makes it
into the build.

I think that's the last MAJOR obstacle to getting OCIO in Fedora. If I
remember correctly (assuming they pass the future unit tests) that the
versions of tinyxml and LCMS already in Fedora are ok?

Thanks,
Richard

[1] https://bugzilla.redhat.com/show_bug.cgi?id=786528

We're looking at 0.3.0  (which maintains the current yaml API).   I talked to the developer, and the new API is a bit too in flux / untested to want to jump to it in the short term.