2022-11-14

Owned by doug walker
Last updated: Nov 14, 2022
2 min read

November 14, 2022

Host: Doug Walker

Secretary: Doug Walker (with notes from Remi)

Attendees:

Rémi Achard (TSC) - DNEG
Mark Boorer (TSC) - Industrial Light & Magic
Mei Chu (TSC) - Sony Pictures Imageworks
Sean Cooper (TSC ACES TAC Rep) - ARRI
Michael Dolan (TSC) - Epic Games
Patrick Hodoul (TSC) - Autodesk
John Mertic - Academy Software Foundation / Linux Foundation
Carol Payne (TSC Chair) - Netflix
Mark Titchener (TSC) - Foundry
Carl Rand (TSC) - Weta Digital
Doug Walker (TSC Chief Architect) - Autodesk
Kevin Wheatley (TSC) - Framestore

Apologies:

  • Carol Payne

  • Mark Titchener

  • Michael Dolan

  • Mei Chu

OCIO TSC Meeting Notes

  • Build issues

    • Doug: I'm working on updating the documentation for 2.2, including the Installation page.

    • We discussed a few CMake warnings and issues with building static libraries. 

      • Doug: I'm trying to understand the warnings we get for Yaml and Pystring when running CMake with -DBUILD_SHARED_LIBS=OFF.

      • Remi: On static libraries, when a static library itself depends on another static library, like OCIO depends on Expat, when you build OCIO statically, it’s going to reference the symbols from Expat but when building an executable or shared library from this static OCIO library, you are still going to need libexpat.a otherwise there will be linker errors. Also you have to pass libOpenColorIO.a then libexpat.a in that order to the linker, otherwise if it finds libexpat.a first and no code use symbols from it at this point, it will just drop everything. CMake hides all that complexity (when it’s correctly set up!).

      • Remi: That’s the way I remember it and why we have warnings in our CMake code to tell you that if you statically build OCIO relying on some in-build dependencies using ExternalProject_Add, you might not be able to compile an app using OCIO on the same system if you don’t provide those required dependencies to the linker.

      • Doug: Makes sense. We should probably add the warnings for the other packages that get downloaded internally too.

    • Remi: Zach posted an issue regarding static compilation with OIIO and OCIO, to improve our CMake config and explicitly look for such static dependencies.  It would be a good one to address soon:

    • Remi: There is a weakness in the current CI where some tests are only done on dynamic:

    • Doug: Cedrik and I will take a look.

  • Issue with API documentation

    • Remi: Any thoughts on how to fix the problem with missing white space in the API documentation?  Doug: One option would be to change the template, do you know of any good ones?  Remi:  We should ask Thomas as he may have a good recommendation.

  • Updating the VFX versions spreadsheet:

  • Items for next meeting agenda:

    • We pushed the items from today's agenda to next time due to the low turn-out.