Date
1 - 3 of 3
Yaml-cpp version / windows build
|
Jeremy Selan <jeremy...@...>
FYI,
The Foundry has successfully gotten OCIO working on Windows, but it required bumping up to the latest stable yaml-cpp version. So just a heads up, that library version will be changing soon. (along with a few other misc. patches). This wont effect binary compatibility - I just wanted to keep people in the loop (for those working on the ext dir). -- Jeremy |
|
|
|
dbr/Ben <dbr....@...>
Sounds good! I seem to recall Malcolm mentioning that an updated yaml-cpp would allow tidying up the config syntax a bit - allowing "-FileTransform{src:blah}" instead of "-!<FileTransform>{src:blah}", maybe? No idea if this is something we'd get "for free", or if it would require code changes, becoming incompatible with existing configs and other bad things... - Ben On 18/05/2011, at 2:33, Jeremy Selan <jeremy...@...> wrote:
|
|
|
|
Jeremy Selan <jeremy...@...>
I verified what the new.ocio output looks like, and the shortened
toggle quoted message
Show quoted text
"-FileTransform" syntax you mention does not appear to be enabled by default, though perhaps there's an additional switch we can set on output to enable it. The only difference between the old output and new output (other than a float precision issue which we addressed with a .patch file) is that when configs are written out, the top line no longer has a bunch of dashes. Old: --- ocio_profile_version: 1 New: ocio_profile_version: 1 I confirmed that both profile syntaxes are interoperable in both the old and new libraries, so this didnt raise a compatibility flag to me. I'm all for enabling a more compact yaml output in 0.9, but for the 0.8 stable build I want to make sure that exported profiles work across all versions. (I'd hate to have an app that uses 0.8.0 not be able to read 0.8.2 exported profiles, which only fail due to this minor syntax change). -- Jeremy On Tue, May 17, 2011 at 5:02 PM, dbr/Ben <dbr....@...> wrote:
Sounds good! |
|
|