Hello, This is my second email to you.
I am building OIIO through Vcpkg, CMake and Visual Studio 2019. Vcpkg currently builds OIIO 2.1.16.0, and I have used "core, libraw, opencolorio, openjpeg, webp, tools" components/flags in building OIIO. I have used the Vcpkg toolchain in CMake to generate the VS solution (projects) for OIIO, and have added the modifications discussed in the first email (reading DPX from memory & fixing Windows long paths) onto OIIO release 2.1.17.0, then built the final "OpenImageIO.dll" and "OpenImageIO_Util.dll". We want to use OIIO in our products that deploy/install on multiple Windows versions (mostly servers): Windows Server 2008 R2, Windows Server 2012 R2, Windows Server 2016, Windows Server 2019, Windows Server 10 different flavors, Windows 7 SP3 -- all 64-bit and our products are 64-bit. While testing on different Windows machines and environments, there is a Windows 10 machine in that OIIO fails to load with the following message: "The procedure entry point SymEnumSymbolsExW could not be located in the dynamic link library C:\WINDOWS\SYSTEM32\dbgeng.dll" The culprit is actually "dbghelp.dll" used by "dbgeng.dll". As an initial fix, I have added "dbghelp.dll" into the installer, but this seems to cause the installer to fail on Win Server 2016. It seems to me that different versions of dbgeng.dll in the OS need specific versions of dbghelp.dll, with other DLL on the cain of dependecies. So, my questions are: * Is there a was to disable the OIIO dependency on "dbgeng.dll" (e.g. a compile switch)? -- this would be our preferred option * If not, has anyone encountered a problem like this and has another fix/workaround? Thank you, Radu Arjocu Software Engineer • Masstech Innovations Inc. • www.masstech.com<http://www.masstech.com><http://www.masstech.com>
_______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
