I ran into the same issue lately and mentioning it on the OpenImageIO Slack caused bewilderment there.
But this is >3.5 years later! Can this pretty please be fixed? A debugh build of OIIO not only pollutes the console as outlined by OP, it is also 1-2 orders of magnitude (!) slower than a release build. The -dev version should ship headers but it should not be built in debug mode. TLDR; you never want to use a debug version of this library unless you are actually developing the library itself as the speed penalty is insane. You can actually just completely drop the `CMAKE_BUILD_TYPE` flag as the default for this is `Release` for the above reason. When someone installs a `-deb` package the common use case is that they are developing some software that uses the library (i.e. links against it). For the specific case where they want to contribute to OIIO they would clone the repo. themselves and create a debug build intentionally anyway. P.S. OIIO 3.0 is now the official stable release (https://openimageio.readthedocs.io/en/stable/) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918351 Title: Build for libopenimageio2.1 package does not appear to be in Release mode... leading to debug output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openimageio/+bug/1918351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
