Thanks for all the help, linking against Nuke's internal libOpenColorIO.so and updating the namespace in the includes to point to FnOpenColorIO worked a charm.
Do we know how the Foundry is compiling OpenColorIO, are they setting the CMake flag -DOpenColorIO=Fn at build time, which should create a conflict free namespace build, or are they editing the header file as I've done? If they are using the CMake flag we should flag this with the OpenColorIO team so they can fix it in the current beta. Cheers On Fri, Mar 11, 2016 at 3:19 AM, Ben Dickson <ben.dick...@rsp.com.au> wrote: > > FnOpenColorIO::v1::ROLE_DEFAULT > > The Foundry build OCIO with a custom namespace "FnOpenColorIO" (not the > default "OpenColorIO") > > With Nuke 8 we replaced both the library and all OCIO nodes with our built > ones and it worked fine. However with Nuke 9 the Nuke executable itself > (well, libnuke) links against OCIO also, which causes the undefined symbol > problem you mention - so we ended up just building with the same > FnOpenColorIO as our changes were compatible > > Not sure if the namespace changed from Nuke 8 to 9, or was just because > libnuke now links to OCIO (because of the greater integration of OCIO into > Nuke Studio, I assume) > > I don't recall if there is an easy way to change the name of the library > itself when building OCIO, but that would be the correct solution to this I > think? > > On 11/03/16 03:29, Josh Imbruglia wrote: > >> Hi Kevin, >> >> I'm running Nuke 9 on Linux, haven't thought to try this with Nuke 8.0, >> that might be an option for testing. We're using gcc 4.9.1 to compile >> all of our plugins and have been for sometime without issue. I've also >> tried attaching it to gdb but doesn't throw an error as it's just a >> silent fail when loading the plugin. I've also ran ldd and it all looks >> correct, linking against our build of OpenColorIO 1.0.9. >> >> I've also removed the OpenColorIO lib from Nuke9 so that it would fall >> back on our compiled version and was getting an undefinted symbol >> FnOpenColorIO::v1::ROLE_DEFAULT which leads me to think there is a >> patched version of OpenColorIO running. >> >> Cheers, >> Josh >> >> On Thu, Mar 10, 2016 at 4:10 PM, Kevin Wheatley >> <kevin.wheat...@framestore.com <mailto:kevin.wheat...@framestore.com>> >> wrote: >> >> On 10 March 2016 at 15:53, Josh Imbruglia >> <the.factory.sm...@gmail.com <mailto:the.factory.sm...@gmail.com>> >> wrote: >> > Hi everybody, >> > >> > I'm wondering if anyone has had success compiling a plugin against >> OCIO. >> > When I link it against an external build of OCIO 1.0.9 I get the >> plugin not >> > loading and failing silently. If I attempt to link it against the >> > libOpenColorIO.so that Nuke was shipped with I get undefined >> reference as >> > I'm using external header files for the include path. Has anyone >> had success >> > with this and have a plugin using an external or internal build of >> > OpenColorIO? >> >> Hi Josh, >> >> What version of Nuke are you using? I had versions of Nuke 8 doing >> this whilst I was adding bits to OCIO previously, I haven't tried with >> Nuke 9, but can't see why it would fail, I'm assuming you've got the >> right compiler versions etc when you built OCIO? Could be a dependent >> library incompatibility, if you are still on Linux I'd check with ldd >> to see what is being pulled in. The other option would be to attach >> gdb to the Nuke process before trying to load it and see if that gives >> any more hints. Usually it will be a symbol problem... >> >> Kevin >> >> -- >> *Framestore* | Kevin Wheatley | Head of Imaging >> *London* - New York - Los Angeles - Montreal >> >> 19-23 Wells Street, London, W1T 3PQ >> T: +44 (0) 20 7344 8000 <tel:%2B44%20%280%29%2020%207344%208000> >> >> framestore.com <http://framestore.com> <http://www.framestore.com/> >> Facebook <https://www.facebook.com/Framestore> >> Twitter <http://twitter.com/Framestore> >> _______________________________________________ >> Nuke-dev mailing list >> Nuke-dev@support.thefoundry.co.uk >> <mailto:Nuke-dev@support.thefoundry.co.uk>, >> http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev >> >> >> >> >> _______________________________________________ >> Nuke-dev mailing list >> Nuke-dev@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev >> >> > -- > ben dickson > 2D TD | ben.dick...@rsp.com.au > rising sun pictures | www.rsp.com.au > > _______________________________________________ > Nuke-dev mailing list > Nuke-dev@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev >
_______________________________________________ Nuke-dev mailing list Nuke-dev@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
