Let me start by first saying how great I think OIIO is, that I am glad you are working on it, and that I am fortunate to be able to use it. Thank you!
My question or problem: I am trying to use openimageio on windows with VS 2019 and vcpkg. At first I was just using the vcpkg build, but I noticed it is a little behind the oiio releases and I need the oiio-to-opencv conversions. So I checked out the latest release 2.1.16 and am building openimageio using my vcpkg toolchain file. The release build is fine. But the debug build is not. Even for core dependencies like imath, my cmake config step is finding the release library when it needs to find the debug one. I am no expert, but I have a reasonable amount of experienced with cmake. Between the complexity of the vcpkg modifications and the custom find modules in oiio, I am at a loss for how to fix my local (non-vpkg) build of oiio using vcpkg (I am using the 2020.01 release of vcpkg.) I have a suspicion a key is in the patches in the vcpkg port for openimageio and particularly the vcpkg-cmake-wrapper.cmake. I believe a fundamental problem is the oiio find module scripts are not working with the vcpkg separation of libraries between x64-windows/lib and x64-windows/debug/lib. In my (limited) understanding of vcpkg, I believe the key to fixing this is to use the vcpkg cmake config scripts. But I am not sure if that is possible or reasonable given the custom find module scripts in openimageio/src/cmake/modules. I sincerely appreciate any help on this matter. Phil
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Oiio-dev mailing list Oiio-dev@lists.openimageio.org http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
