Hello, I'm trying to update the deep exr reader and writer so that it can support a different file extension. I had to modify the exrWriterDeep in a couple of places (removed the include for ImfMisc.h, replaced calls to pixelTypeSize with regular sizeof calls, and replaced Foundry::Type::AtomicCount32 with std::atomic_int) but other than that everything builds fine. Of course building and loading are two different things. Beyond some namespace difference in the openexr 2.0 build that I've created it appears that the libstdc++.so.6 on my system is newer than what is shipped with nuke so I'm unable to load a plugin with a custom openexr build (which uses a namespace that won't conflict with the version shipped with Nuke).
If I link directly to the openexr 2.0 build that ships with Nuke I have a problem with a couple of versions of the Imf::TypedAttribute<>::writeValueTo method. As an example: Nuke/7.0v4-64/libIlmImf-Imf_2_0_0.so.20 exports the following: Imf_2_0_0::TypedAttribute<Imath::Matrix44<float>, Imf_2_0_0::Attribute>::writeValueTo(Imf_2_0_0::OStream&, int) const The version of the plugin I'm building is looking for this symbol a bit differently: Imf_2_0_0::TypedAttribute<Imath::Matrix44<float> >::writeValueTo(Imf_2_0_0::OStream&, int) const Would anyone be able to share the options passed to the openexr configure script used to build Nukes version? Or share what version of GCC is used to build Nuke? Thanks! Chip _______________________________________________ Nuke-dev mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
