ocio-dev@lists.aswf.io | Build error on CentOS 7.5

Home Messages Hashtags Subgroups Calendar

Date Date 1 - 3 of 3

Build error on CentOS 7.5

noizf...@... #1735 Hi, I'm using a CentOS 7.5 (3.10.0-693.2.2.el7.x86_64) docker instance to build ocio with devtoolset-6 and my build fails with the following error: /oss/imageworks/OpenColorIO/src/apps/ocioconvert/main.cpp: In function 'int main(int, const char*)': /oss/imageworks/OpenColorIO/src/apps/ocioconvert/main.cpp:122:66: error: cannot convert 'OpenImageIO_v1_9::ImageInput::unique_ptr {aka std::unique_ptr<OpenImageIO_v1_9::ImageInput>}' to 'OpenImageIO_v1_9::ImageInput' in initialization OIIO::ImageInput* f = OIIO::ImageInput::create(inputimage); ^ /oss/imageworks/OpenColorIO/src/apps/ocioconvert/main.cpp:311:69: error: cannot convert 'OpenImageIO_v1_9::ImageOutput::unique_ptr {aka std::unique_ptr<OpenImageIO_v1_9::ImageOutput>}' to 'OpenImageIO_v1_9::ImageOutput' in initialization OIIO::ImageOutput f = OIIO::ImageOutput::create(outputimage); I also get these warnings initially during the build but not sure if they eventually cause the build to error out? `/oss/imageworks/OpenColorIO/build/ext/yaml-cpp/src/ptr_stack.h:35:8: warning: 'template<class> class std::auto_ptr' is deprecated [-Wdeprecated-declarations] std::auto_ptr<T> t(m_data.back());` I'm following the build instructions on this page. I have already built oiio and its installed in the default system location and ocio is picking that up correctly during the build process. But I came across this post re the cyclic dependency issue between ocio and oiio and I'm wondering if I need to follow the instructions on that thread in Linux as well since I intend to build all the ocio apps? Thanks, Sachin
More
Larry Gritz <l...@...> #1736 Yeah, I'm sorry, in OIIO master branch (the next release, in development), there has been an API change that OCIO has not yet caught up with. That's my fault, it's on my list to fix right away. In the mean time, OCIO requires OIIO 1.8 (the current official stable release) or earlier, if you are building ocioconverr and the other command-line utilities. (OCIO's core library doesn't have any OIIO dependency at all.) -- lg On Sep 26, 2018, at 12:21 AM, noizf...@... wrote: Hi, I'm using a CentOS 7.5 (3.10.0-693.2.2.el7.x86_64) docker instance to build ocio with devtoolset-6 and my build fails with the following error: /oss/imageworks/OpenColorIO/src/apps/ocioconvert/main.cpp: In function 'int main(int, const char*)': /oss/imageworks/OpenColorIO/src/apps/ocioconvert/main.cpp:122:66: error: cannot convert 'OpenImageIO_v1_9::ImageInput::unique_ptr {aka std::unique_ptr<OpenImageIO_v1_9::ImageInput>}' to 'OpenImageIO_v1_9::ImageInput' in initialization OIIO::ImageInput* f = OIIO::ImageInput::create(inputimage); ^ /oss/imageworks/OpenColorIO/src/apps/ocioconvert/main.cpp:311:69: error: cannot convert 'OpenImageIO_v1_9::ImageOutput::unique_ptr {aka std::unique_ptr<OpenImageIO_v1_9::ImageOutput>}' to 'OpenImageIO_v1_9::ImageOutput' in initialization OIIO::ImageOutput f = OIIO::ImageOutput::create(outputimage); I also get these warnings initially during the build but not sure if they eventually cause the build to error out? `/oss/imageworks/OpenColorIO/build/ext/yaml-cpp/src/ptr_stack.h:35:8: warning: 'template<class> class std::auto_ptr' is deprecated [-Wdeprecated-declarations] std::auto_ptr<T> t(m_data.back());` I'm following the build instructions on this page. I have already built oiio and its installed in the default system location and ocio is picking that up correctly during the build process. But I came across this post re the cyclic dependency issue between ocio and oiio and I'm wondering if I need to follow the instructions on that thread in Linux as well since I intend to build all the ocio apps? Thanks, Sachin -- You received this message because you are subscribed to the Google Groups "OpenColorIO Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to ocio-dev+u...@.... For more options, visit https://groups.google.com/d/optout. -- Larry Gritz l...@...
More
Sachin Shrestha <noizf...@...> #1737 Thanks Larry, I realised that too after posting this and managed to build it with 1.8. The ociotools got compiled properly too. Thanks, Sachin toggle quoted message Show quoted text On Wed, 26 Sep 2018 at 23:09, Larry Gritz <l...@...> wrote: Yeah, I'm sorry, in OIIO master branch (the next release, in development), there has been an API change that OCIO has not yet caught up with. That's my fault, it's on my list to fix right away. In the mean time, OCIO requires OIIO 1.8 (the current official stable release) or earlier, if you are building ocioconverr and the other command-line utilities. (OCIO's core library doesn't have any OIIO dependency at all.) -- lg On Sep 26, 2018, at 12:21 AM, noizf...@... wrote: Hi, I'm using a CentOS 7.5 (3.10.0-693.2.2.el7.x86_64) docker instance to build ocio with devtoolset-6 and my build fails with the following error: /oss/imageworks/OpenColorIO/src/apps/ocioconvert/main.cpp: In function 'int main(int, const char*)': /oss/imageworks/OpenColorIO/src/apps/ocioconvert/main.cpp:122:66: error: cannot convert 'OpenImageIO_v1_9::ImageInput::unique_ptr {aka std::unique_ptr<OpenImageIO_v1_9::ImageInput>}' to 'OpenImageIO_v1_9::ImageInput' in initialization OIIO::ImageInput* f = OIIO::ImageInput::create(inputimage); ^ /oss/imageworks/OpenColorIO/src/apps/ocioconvert/main.cpp:311:69: error: cannot convert 'OpenImageIO_v1_9::ImageOutput::unique_ptr {aka std::unique_ptr<OpenImageIO_v1_9::ImageOutput>}' to 'OpenImageIO_v1_9::ImageOutput' in initialization OIIO::ImageOutput f = OIIO::ImageOutput::create(outputimage); I also get these warnings initially during the build but not sure if they eventually cause the build to error out? `/oss/imageworks/OpenColorIO/build/ext/yaml-cpp/src/ptr_stack.h:35:8: warning: 'template<class> class std::auto_ptr' is deprecated [-Wdeprecated-declarations] std::auto_ptr<T> t(m_data.back());` I'm following the build instructions on this page. I have already built oiio and its installed in the default system location and ocio is picking that up correctly during the build process. But I came across this post re the cyclic dependency issue between ocio and oiio and I'm wondering if I need to follow the instructions on that thread in Linux as well since I intend to build all the ocio apps? Thanks, Sachin -- You received this message because you are subscribed to the Google Groups "OpenColorIO Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to ocio-dev+u...@.... For more options, visit https://groups.google.com/d/optout. -- Larry Gritz l...@... -- You received this message because you are subscribed to the Google Groups "OpenColorIO Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to ocio-dev+u...@.... For more options, visit https://groups.google.com/d/optout.
More

1 - 3 of 3

1

Previous Topic Next Topic

Home Hashtags Subgroups Calendar Terms