Problem summary The way libOpenColorIO is built for Nuke does not limit the exporting of symbols, particularly from the yaml-cpp dependency. This means that users can suffer symbol collision when they have their own yaml-cpp.
Customer reported version Nuke 12.1v5
Customer reported platform CentOS 7
Expected behaviour Users should be able to have their own yaml-cpp, without any symbol collisons.
Actual behaviour Users can suffer symbol collision when they have their own yaml-cpp.
Workaround Unknown.
Reproduced by support This bug has been identified by our developers in Nuke 12.1v5, but is also present in Nuke 12.2.