So it turns out my issue was a permission error. When I logged in with the (hidden built-in) Administrator account and reinstalled everything, packages started to build correctly. I'm sure how/why cmake tries to create files in the root of the C drive though.
I'm using the new build files from the github post by Chris, and I can get it to build with both openimageio[tools]:x64-windows and openimage[tools]:x64-windows-static. The command line tools seems to work well. However, I can't get the Python bindings to work. I found out I needed to install Pybind11 before OpenImageIO and from what I understand I also need to edit the portfile.cmake for pybind to use Python2 instead of Python3. Right? If I do so and enable the DUSE_PYTHON I get the python bindings to build without errors (both dynamic and static). But when I try to use them it doesn't work. The static one gives a "Fatal python error" and the dynamic one complains about missing dll:s, even though I copied the dlls to the same folder and added everything to the pythonpath. Any ideas? ------------------------------- Simon Björk Compositor/TD +46 (0)70-2859503 www.bjorkvisuals.com Den sön 29 dec. 2019 kl 15:28 skrev Chris <ch...@digitaldevoid.com>: > Hi simon > > I’m still muddling my way through. Im porting my app from c11 on Mac to > windows & linux, and aside from OIIO I have other issues on windows, so I > have not linked the . Obj files yet > > Yes, those missing openexr > Dlls May need to be in your path or app dir. they get built, check > installed dir I think. I thought my default port files build both OIIO > static & shared, but I may be mistaken. Check the bin dir for dlls > > Yes, the oiio tools are definitely shared builds. Yes my python builds, > but I’m not directly using them. I think they were needed for the QT 5 > build, or opencv, not sure. > > I’m using Msvc ver 16.4.2 now. It works, and have not bothered rebuilding > all the libs from 15.9 > > Still getting vcpkg log errors about some plugins, but not having run my > app nor tools not sure if they are valid as the libs seem to have been > built. > > Sorry I couldn’t offer more concrete stuff, like you, getting there. > Windows is a POS > > > > Chris Spence > Digital Devoid > 7300 Biscayne Blvd., Suite 405 > Miami, FL 33138 > > 305 757 1330 > > ch...@digitaldevoid.com > www.digitaldevoid.com > > > > On Dec 28, 2019, at 5:25 PM, Simon Björk <bjork.si...@gmail.com> wrote: > > Hi Chris, > > thanks for the follow up on this. I'm now testing on a third computer and > it's looking quite promising using the updated ports from your github > issue. Some questions though: > > - Should I use the x64-windows-static option when building? If I don't, > tools like oiiotool complains about missing dlls (exr stuff, png stuff > etc). If I use the static option it seems to work (but then I don't seem to > get a OpenImageIO.dll at all? > > - If I change DUSE_PYTHON and DBUILD_MISSING_PYBIND11 to ON, I assumed it > would create the python bindings. But if I do, the build fails. I also > tried to install pybind11 before building openimageio but it still fails. > Have you had any success with the python bindings? > > /Simon > > > > ------------------------------- > Simon Björk > Compositor/TD > > +46 (0)70-2859503 > www.bjorkvisuals.com > > > Den ons 25 dec. 2019 kl 16:47 skrev Chris Spence <ch...@digitaldevoid.com > >: > >> Hi Simon, >> >> Just wanted to pass onto you my status: >> >> Part of my problem stems from outdated ports, & builds. I’m new to vcpkg, >> that is - I was unaware that after installation - one should do : once vcpkg >> has been cloned & installed (directly from GitHub >> <https://github.com/microsoft/vcpkg>), use "git pull" to update the >> list of portfiles. Once you've updated your portfiles, "vcpkg update" >> will indicate any installed libraries that are now out of date. >> >> Not being aware, I had failed to do the above after vcpkg install, and >> only now are re-building the OIIO dependent/non-dependent libs as there >> were a ton of outdated ports. >> >> Here’s my post on my issues (see last entry): >> >> https://github.com/microsoft/vcpkg/issues/9377 >> >> So VS 2019, ver 16.2.5 works in building OIIO libs (from VS 2017 15.9 >> compiled dependent libs). So - based on comments on GitHub. - I would >> imagine ver 16.4 also works, and by extension Community 16.4. I also read >> that all 14.xx version libs are binary compatible, so that 14.0, 14.1, 14.2 >> libs can be mixed. In my case, and in your case, I’d recommend using 14.1 >> (as I know that works). >> >> Later >> >> Chris Spence >> Digital Devoid, Inc. >> 7300 Biscayne Blvd, Suite 405 >> Miami, FL 33138 >> >> Tel: 305 757 1330 >> >> ch...@digitaldevoid.com >> www.digitaldevoid.com >> >> On Dec 19, 2019, at 8:40 AM, Simon Björk <bjork.si...@gmail.com> wrote: >> >> Sorry for the spam, this is most likely me not knowing how to use >> vcpkg/cmake. >> >> If I deleted the VCPKG_PLATFORM_TOOLSET v140 line and deleted >> CmakeCache.txt, it no longer search for 2014. However it still fails. >> Curious to see if anyone else have this working with Visual Studio 2019. >> >> Error: >> >> >> [1/1] cmd /c "cd .. && "D:/sandbox/vcpkg/downloads/tools/cmake-3.14.0 >> -windows/cmake-3.14.0-win32-x86/bin/cmake.exe" "D:/sandbox/ >> vcpkg/buildtrees/zlib/src/1.2.11-f690224aeb" "-DSKIP_INSTALL_FILES=ON" " >> -DSKIP_BUILD_EXAMPLES=ON" "-DCMAKE_MAKE_PROGRAM=C:/Program Files >> (x86)/Microsoft >> Visual Studio/2019 >> /Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" >> "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=D:/sandbox/ >> vcpkg/scripts/toolchains/windows.cmake" " >> -DVCPKG_TARGET_TRIPLET=x64-windows" "-DVCPKG_SET_CHARSET_FLAG=ON" " >> -DVCPKG_PLATFORM_TOOLSET=v142" "-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON" " >> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON" " >> -DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON" " >> -DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE" " >> -DCMAKE_VERBOSE_MAKEFILE=ON" "-DVCPKG_APPLOCAL_DEPS=OFF" " >> -DCMAKE_TOOLCHAIN_FILE=D:/sandbox/vcpkg/scripts/buildsystems/vcpkg.cmake" >> "-DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON" "-DVCPKG_CXX_FLAGS=" " >> -DVCPKG_CXX_FLAGS_RELEASE=" "-DVCPKG_CXX_FLAGS_DEBUG=" "-DVCPKG_C_FLAGS=" >> "-DVCPKG_C_FLAGS_RELEASE=" "-DVCPKG_C_FLAGS_DEBUG=" " >> -DVCPKG_CRT_LINKAGE=dynamic" "-DVCPKG_LINKER_FLAGS=" " >> -DVCPKG_TARGET_ARCHITECTURE=x64" "-DCMAKE_INSTALL_LIBDIR:STRING=lib" " >> -DCMAKE_INSTALL_BINDIR:STRING=bin" "-G" "Ninja" " >> -DCMAKE_BUILD_TYPE=Release" "-DCMAKE_INSTALL_PREFIX=D:/sandbox/ >> vcpkg/packages/zlib_x64-windows"" >> FAILED: ../CMakeCache.txt >> cmd /c "cd .. && "D:/sandbox/vcpkg/downloads/tools/cmake-3.14.0 >> -windows/cmake-3.14.0-win32-x86/bin/cmake.exe" "D:/sandbox/ >> vcpkg/buildtrees/zlib/src/1.2.11-f690224aeb" "-DSKIP_INSTALL_FILES=ON" " >> -DSKIP_BUILD_EXAMPLES=ON" "-DCMAKE_MAKE_PROGRAM=C:/Program Files >> (x86)/Microsoft >> Visual Studio/2019 >> /Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" >> "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=D:/sandbox/ >> vcpkg/scripts/toolchains/windows.cmake" " >> -DVCPKG_TARGET_TRIPLET=x64-windows" "-DVCPKG_SET_CHARSET_FLAG=ON" " >> -DVCPKG_PLATFORM_TOOLSET=v142" "-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON" " >> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON" " >> -DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON" " >> -DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE" " >> -DCMAKE_VERBOSE_MAKEFILE=ON" "-DVCPKG_APPLOCAL_DEPS=OFF" " >> -DCMAKE_TOOLCHAIN_FILE=D:/sandbox/vcpkg/scripts/buildsystems/vcpkg.cmake" >> "-DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON" "-DVCPKG_CXX_FLAGS=" " >> -DVCPKG_CXX_FLAGS_RELEASE=" "-DVCPKG_CXX_FLAGS_DEBUG=" "-DVCPKG_C_FLAGS=" >> "-DVCPKG_C_FLAGS_RELEASE=" "-DVCPKG_C_FLAGS_DEBUG=" " >> -DVCPKG_CRT_LINKAGE=dynamic" "-DVCPKG_LINKER_FLAGS=" " >> -DVCPKG_TARGET_ARCHITECTURE=x64" "-DCMAKE_INSTALL_LIBDIR:STRING=lib" " >> -DCMAKE_INSTALL_BINDIR:STRING=bin" "-G" "Ninja" " >> -DCMAKE_BUILD_TYPE=Release" "-DCMAKE_INSTALL_PREFIX=D:/sandbox/ >> vcpkg/packages/zlib_x64-windows"" >> CMake Warning at ../../../../scripts/buildsystems/vcpkg.cmake:104 >> (message): >> There are no libraries installed for the Vcpkg triplet x64-windows. >> Call Stack (most recent call first): >> ../../../../downloads/tools/cmake-3.14.0-windows/cmake-3.14.0 >> -win32-x86/share/cmake-3.14/Modules/CMakeDetermineSystem.cmake:93 >> (include) >> CMakeLists.txt:4 (project) >> >> >> -- The C compiler identification is MSVC 19.24.28314.0 >> -- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual >> Studio/2019/Community/VC/Tools/MSVC/14.24.28314/bin/Hostx64/x64/cl.exe >> -- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual >> Studio/2019/Community/VC/Tools/MSVC/14.24.28314/bin/Hostx64/x64/cl.exe >> -- broken >> CMake Error at ../../../../downloads/tools/cmake-3.14.0-windows/cmake >> -3.14.0-win32-x86/share/cmake-3.14/Modules/CMakeTestCCompiler.cmake:60 >> (message): >> The C compiler >> >> "C:/Program Files (x86)/Microsoft Visual >> Studio/2019/Community/VC/Tools/MSVC/14.24.28314/bin/Hostx64/x64/cl.exe" >> >> is not able to compile a simple test program. >> >> It fails with the following output: >> >> Change Dir: D://CMakeFiles/CMakeTmp >> >> Run Build Command(s):C:/Program Files (x86)/Microsoft Visual >> Studio/2019/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe >> cmTC_4ff2d >> [1/2] Building C object CMakeFiles\cmTC_4ff2d.dir\testCCompiler.c.obj >> [2/2] Linking C executable cmTC_4ff2d.exe >> FAILED: cmTC_4ff2d.exe >> cmd.exe /C "cd . && >> D:\sandbox\vcpkg\downloads\tools\cmake-3.14.0-windows\cmake-3.14.0-win32-x86\bin\cmake.exe >> -E vs_link_exe --intdir=CMakeFiles\cmTC_4ff2d.dir >> --rc=C:\PROGRA~2\WI3CF2~1\10\bin\100183~1.0\x64\rc.exe >> --mt=C:\PROGRA~2\WI3CF2~1\10\bin\100183~1.0\x64\mt.exe --manifests -- >> C:\PROGRA~2\MICROS~1\2019\COMMUN~1\VC\Tools\MSVC\1424~1.283\bin\Hostx64\x64\link.exe >> /nologo CMakeFiles\cmTC_4ff2d.dir\testCCompiler.c.obj /out:cmTC_4ff2d.exe >> /implib:cmTC_4ff2d.lib /pdb:cmTC_4ff2d.pdb /version:0.0 /machine:x64 >> /debug /INCREMENTAL /subsystem:console kernel32.lib user32.lib gdi32.lib >> winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib >> advapi32.lib && cd ." >> ninja: build stopped: subcommand failed. >> >> >> >> >> CMake will not be able to correctly generate this project. >> Call Stack (most recent call first): >> CMakeLists.txt:4 (project) >> >> >> -- Configuring incomplete, errors occurred! >> See also "D://CMakeFiles/CMakeOutput.log". >> See also "D://CMakeFiles/CMakeError.log". >> ninja: build stopped: subcommand failed. >> >> >> >> >> >> ------------------------------- >> Simon Björk >> Compositor/TD >> >> +46 (0)70-2859503 >> www.bjorkvisuals.com >> >> >> Den tors 19 dec. 2019 kl 14:29 skrev Simon Björk <bjork.si...@gmail.com>: >> >>> Donat: Ah good catch, but be a leftover from the last time I tried. I >>> deleted tose folder and reinstalled everything. It still failes, but now >>> with a different error (still while building zlib, the first thing it tries >>> to build). >>> >>> Looking at the log file, it seems to be looking for Visual Studio 14 for >>> whatever reason? Not sure why this is. I'm using 2019 (as that's the only >>> one I can download). >>> >>> Chris: Please update if 2019 works for you. >>> >>> Below is the log file: >>> >>> >>> [1/1] cmd /c "cd .. && "D:/sandbox/vcpkg/downloads/tools/cmake-3.14.0 >>> -windows/cmake-3.14.0-win32-x86/bin/cmake.exe" "D:/sandbox/ >>> vcpkg/buildtrees/zlib/src/1.2.11-f690224aeb" "-DSKIP_INSTALL_FILES=ON" " >>> -DSKIP_BUILD_EXAMPLES=ON" "-DCMAKE_MAKE_PROGRAM=C:/Program Files >>> (x86)/Microsoft >>> Visual Studio/2019 >>> /Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" >>> "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=D:/sandbox/ >>> vcpkg/scripts/toolchains/windows.cmake" " >>> -DVCPKG_TARGET_TRIPLET=x64-windows" "-DVCPKG_SET_CHARSET_FLAG=ON" " >>> -DVCPKG_PLATFORM_TOOLSET=v142" "-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON" " >>> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON" " >>> -DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON" " >>> -DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE" " >>> -DCMAKE_VERBOSE_MAKEFILE=ON" "-DVCPKG_APPLOCAL_DEPS=OFF" " >>> -DCMAKE_TOOLCHAIN_FILE=D:/sandbox/vcpkg/scripts/buildsystems/vcpkg.cmake" >>> "-DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON" "-DVCPKG_CXX_FLAGS=" >>> "-DVCPKG_CXX_FLAGS_RELEASE=" "-DVCPKG_CXX_FLAGS_DEBUG=" " >>> -DVCPKG_C_FLAGS=" "-DVCPKG_C_FLAGS_RELEASE=" "-DVCPKG_C_FLAGS_DEBUG=" " >>> -DVCPKG_CRT_LINKAGE=dynamic" "-DVCPKG_LINKER_FLAGS=" " >>> -DVCPKG_TARGET_ARCHITECTURE=x64" "-DCMAKE_INSTALL_LIBDIR:STRING=lib" " >>> -DCMAKE_INSTALL_BINDIR:STRING=bin" "-G" "Ninja" " >>> -DCMAKE_BUILD_TYPE=Release" "-DCMAKE_INSTALL_PREFIX=D:/sandbox/ >>> vcpkg/packages/zlib_x64-windows"" >>> FAILED: ../CMakeCache.txt >>> cmd /c "cd .. && "D:/sandbox/vcpkg/downloads/tools/cmake-3.14.0 >>> -windows/cmake-3.14.0-win32-x86/bin/cmake.exe" "D:/sandbox/ >>> vcpkg/buildtrees/zlib/src/1.2.11-f690224aeb" "-DSKIP_INSTALL_FILES=ON" " >>> -DSKIP_BUILD_EXAMPLES=ON" "-DCMAKE_MAKE_PROGRAM=C:/Program Files >>> (x86)/Microsoft >>> Visual Studio/2019 >>> /Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" >>> "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=D:/sandbox/ >>> vcpkg/scripts/toolchains/windows.cmake" " >>> -DVCPKG_TARGET_TRIPLET=x64-windows" "-DVCPKG_SET_CHARSET_FLAG=ON" " >>> -DVCPKG_PLATFORM_TOOLSET=v142" "-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON" " >>> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON" " >>> -DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON" " >>> -DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE" " >>> -DCMAKE_VERBOSE_MAKEFILE=ON" "-DVCPKG_APPLOCAL_DEPS=OFF" " >>> -DCMAKE_TOOLCHAIN_FILE=D:/sandbox/vcpkg/scripts/buildsystems/vcpkg.cmake" >>> "-DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON" "-DVCPKG_CXX_FLAGS=" >>> "-DVCPKG_CXX_FLAGS_RELEASE=" "-DVCPKG_CXX_FLAGS_DEBUG=" " >>> -DVCPKG_C_FLAGS=" "-DVCPKG_C_FLAGS_RELEASE=" "-DVCPKG_C_FLAGS_DEBUG=" " >>> -DVCPKG_CRT_LINKAGE=dynamic" "-DVCPKG_LINKER_FLAGS=" " >>> -DVCPKG_TARGET_ARCHITECTURE=x64" "-DCMAKE_INSTALL_LIBDIR:STRING=lib" " >>> -DCMAKE_INSTALL_BINDIR:STRING=bin" "-G" "Ninja" " >>> -DCMAKE_BUILD_TYPE=Release" "-DCMAKE_INSTALL_PREFIX=D:/sandbox/ >>> vcpkg/packages/zlib_x64-windows"" >>> CMake Warning at ../../../../scripts/buildsystems/vcpkg.cmake:104 >>> (message): >>> There are no libraries installed for the Vcpkg triplet x64-windows. >>> Call Stack (most recent call first): >>> ../../../../../../CMakeFiles/3.14.0/CMakeSystem.cmake:6 (include) >>> CMakeLists.txt:4 (project) >>> >>> >>> -- The C compiler identification is MSVC 19.0.24245.0 >>> -- Check for working C compiler: C:/Program Files (x86)/Microsoft >>> Visual Studio 14.0/VC/bin/amd64/cl.exe >>> -- Check for working C compiler: C:/Program Files (x86)/Microsoft >>> Visual Studio 14.0/VC/bin/amd64/cl.exe -- broken >>> CMake Error at ../../../../downloads/tools/cmake-3.14.0-windows/cmake >>> -3.14.0-win32-x86/share/cmake-3.14/Modules/CMakeTestCCompiler.cmake:60 >>> (message): >>> The C compiler >>> >>> "C:/Program Files (x86)/Microsoft Visual Studio >>> 14.0/VC/bin/amd64/cl.exe" >>> >>> is not able to compile a simple test program. >>> >>> It fails with the following output: >>> >>> Change Dir: D://CMakeFiles/CMakeTmp >>> >>> Run Build Command(s):C:/Program Files (x86)/Microsoft Visual >>> Studio/2019/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe >>> cmTC_3b6f8 >>> [1/2] Building C object CMakeFiles\cmTC_3b6f8.dir\testCCompiler.c.obj >>> [2/2] Linking C executable cmTC_3b6f8.exe >>> FAILED: cmTC_3b6f8.exe >>> cmd.exe /C "cd . && >>> D:\sandbox\vcpkg\downloads\tools\cmake-3.14.0-windows\cmake-3.14.0-win32-x86\bin\cmake.exe >>> -E vs_link_exe --intdir=CMakeFiles\cmTC_3b6f8.dir >>> --rc=C:\PROGRA~2\WI3CF2~1\10\bin\100183~1.0\x64\rc.exe >>> --mt=C:\PROGRA~2\WI3CF2~1\10\bin\100183~1.0\x64\mt.exe --manifests -- >>> C:\PROGRA~2\MICROS~1.0\VC\bin\amd64\link.exe /nologo >>> CMakeFiles\cmTC_3b6f8.dir\testCCompiler.c.obj /out:cmTC_3b6f8.exe >>> /implib:cmTC_3b6f8.lib /pdb:cmTC_3b6f8.pdb /version:0.0 /machine:x64 >>> /debug /INCREMENTAL /subsystem:console kernel32.lib user32.lib gdi32.lib >>> winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib >>> advapi32.lib && cd ." >>> ninja: build stopped: subcommand failed. >>> >>> >>> >>> >>> CMake will not be able to correctly generate this project. >>> Call Stack (most recent call first): >>> CMakeLists.txt:4 (project) >>> >>> >>> -- Configuring incomplete, errors occurred! >>> See also "D://CMakeFiles/CMakeOutput.log". >>> See also "D://CMakeFiles/CMakeError.log". >>> ninja: build stopped: subcommand failed. >>> >>> >>> >>> >>> >>> ------------------------------- >>> Simon Björk >>> Compositor/TD >>> >>> +46 (0)70-2859503 >>> www.bjorkvisuals.com >>> >>> >>> Den tors 19 dec. 2019 kl 10:00 skrev Donat Van Bellinghen < >>> do...@nozon.com>: >>> >>>> Hi Chris, >>>> >>>> When you downloaded vcpkg, did you download the master branch or a >>>> release tag (the latest release tag is 2019.11). I don't know if matters >>>> that much, but I used the 2019.11 release. >>>> What I find strange in your log is that vcpkg seems to be installed in >>>> two separate folders : >>>> D:/dev/vcpkg/... and D:/tmp/vcpkg/... >>>> In my case everything was in a single folder >>>> >>>> Donat >>>> >>>> On 18-12-19 23:08, Simon Björk wrote: >>>> >>>> Hi Chris, >>>> >>>> thans for your reply. Are you saying you can get OIIO to build with >>>> libtiff if yout build libtiff before executing the build command in vcpkg? >>>> Where does vcpkg it look for those extra libs in that case? >>>> >>>> Also, I tried installing via vcpkg and got the same error as I got the >>>> last time I tried (and gave up). Not sure what it is, maybe something >>>> really basic? It seems to happen for any package I try to install, in this >>>> case I ran *vcpkg install freetype:x64-windows*. First it downloads >>>> cmake, then tries to build zlib, and then failes with "Command failed: >>>> ninja -v". I remember seeing the exact same error for other packages. I'll >>>> pase the content of config-x64-windows-out.log below, maybe somebody have >>>> seen this before? >>>> >>>> [1/2] cmd /c "cd ../../x64-windows-dbg && "D:/dev/ >>>> vcpkg/downloads/tools/cmake-3.14.0-windows/cmake-3.14.0 >>>> -win32-x86/bin/cmake.exe" "D:/dev/vcpkg/buildtrees/zlib/src/1.2.11 >>>> -f690224aeb" "-DSKIP_INSTALL_FILES=ON" "-DSKIP_BUILD_EXAMPLES=ON" " >>>> -DCMAKE_MAKE_PROGRAM=C:/Program Files (x86)/Microsoft Visual Studio/ >>>> 2019 >>>> /Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" >>>> "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=D:/dev/ >>>> vcpkg/scripts/toolchains/windows.cmake" " >>>> -DVCPKG_TARGET_TRIPLET=x64-windows" "-DVCPKG_SET_CHARSET_FLAG=ON" " >>>> -DVCPKG_PLATFORM_TOOLSET=v142" "-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON" >>>> "-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON" " >>>> -DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON" " >>>> -DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE" " >>>> -DCMAKE_VERBOSE_MAKEFILE=ON" "-DVCPKG_APPLOCAL_DEPS=OFF" " >>>> -DCMAKE_TOOLCHAIN_FILE=D:/dev/vcpkg/scripts/buildsystems/vcpkg.cmake" " >>>> -DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON" "-DVCPKG_CXX_FLAGS=" >>>> "-DVCPKG_CXX_FLAGS_RELEASE=" "-DVCPKG_CXX_FLAGS_DEBUG=" " >>>> -DVCPKG_C_FLAGS=" "-DVCPKG_C_FLAGS_RELEASE=" "-DVCPKG_C_FLAGS_DEBUG=" " >>>> -DVCPKG_CRT_LINKAGE=dynamic" "-DVCPKG_LINKER_FLAGS=" " >>>> -DVCPKG_TARGET_ARCHITECTURE=x64" "-DCMAKE_INSTALL_LIBDIR:STRING=lib" " >>>> -DCMAKE_INSTALL_BINDIR:STRING=bin" "-DSKIP_INSTALL_HEADERS=ON" "-G" " >>>> Ninja" "-DCMAKE_BUILD_TYPE=Debug" "-DCMAKE_INSTALL_PREFIX=D:/dev/ >>>> vcpkg/packages/zlib_x64-windows/debug"" >>>> FAILED: ../../x64-windows-dbg/CMakeCache.txt >>>> cmd /c "cd ../../x64-windows-dbg && "D:/dev/vcpkg/downloads/tools/cmake >>>> -3.14.0-windows/cmake-3.14.0-win32-x86/bin/cmake.exe" "D:/dev/ >>>> vcpkg/buildtrees/zlib/src/1.2.11-f690224aeb" "-DSKIP_INSTALL_FILES=ON" >>>> "-DSKIP_BUILD_EXAMPLES=ON" "-DCMAKE_MAKE_PROGRAM=C:/Program Files >>>> (x86)/Microsoft Visual Studio/2019 >>>> /Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" >>>> "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=D:/dev/ >>>> vcpkg/scripts/toolchains/windows.cmake" " >>>> -DVCPKG_TARGET_TRIPLET=x64-windows" "-DVCPKG_SET_CHARSET_FLAG=ON" " >>>> -DVCPKG_PLATFORM_TOOLSET=v142" "-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON" >>>> "-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON" " >>>> -DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON" " >>>> -DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE" " >>>> -DCMAKE_VERBOSE_MAKEFILE=ON" "-DVCPKG_APPLOCAL_DEPS=OFF" " >>>> -DCMAKE_TOOLCHAIN_FILE=D:/dev/vcpkg/scripts/buildsystems/vcpkg.cmake" " >>>> -DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON" "-DVCPKG_CXX_FLAGS=" >>>> "-DVCPKG_CXX_FLAGS_RELEASE=" "-DVCPKG_CXX_FLAGS_DEBUG=" " >>>> -DVCPKG_C_FLAGS=" "-DVCPKG_C_FLAGS_RELEASE=" "-DVCPKG_C_FLAGS_DEBUG=" " >>>> -DVCPKG_CRT_LINKAGE=dynamic" "-DVCPKG_LINKER_FLAGS=" " >>>> -DVCPKG_TARGET_ARCHITECTURE=x64" "-DCMAKE_INSTALL_LIBDIR:STRING=lib" " >>>> -DCMAKE_INSTALL_BINDIR:STRING=bin" "-DSKIP_INSTALL_HEADERS=ON" "-G" " >>>> Ninja" "-DCMAKE_BUILD_TYPE=Debug" "-DCMAKE_INSTALL_PREFIX=D:/dev/ >>>> vcpkg/packages/zlib_x64-windows/debug"" >>>> The system cannot find the path specified. >>>> [2/2] cmd /c "cd .. && "D:/dev/vcpkg/downloads/tools/cmake-3.14.0 >>>> -windows/cmake-3.14.0-win32-x86/bin/cmake.exe" "D:/dev/ >>>> vcpkg/buildtrees/zlib/src/1.2.11-f690224aeb" "-DSKIP_INSTALL_FILES=ON" >>>> "-DSKIP_BUILD_EXAMPLES=ON" "-DCMAKE_MAKE_PROGRAM=C:/Program Files >>>> (x86)/Microsoft Visual Studio/2019 >>>> /Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" >>>> "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=D:/dev/ >>>> vcpkg/scripts/toolchains/windows.cmake" " >>>> -DVCPKG_TARGET_TRIPLET=x64-windows" "-DVCPKG_SET_CHARSET_FLAG=ON" " >>>> -DVCPKG_PLATFORM_TOOLSET=v142" "-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON" >>>> "-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON" " >>>> -DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON" " >>>> -DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE" " >>>> -DCMAKE_VERBOSE_MAKEFILE=ON" "-DVCPKG_APPLOCAL_DEPS=OFF" " >>>> -DCMAKE_TOOLCHAIN_FILE=D:/dev/vcpkg/scripts/buildsystems/vcpkg.cmake" " >>>> -DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON" "-DVCPKG_CXX_FLAGS=" >>>> "-DVCPKG_CXX_FLAGS_RELEASE=" "-DVCPKG_CXX_FLAGS_DEBUG=" " >>>> -DVCPKG_C_FLAGS=" "-DVCPKG_C_FLAGS_RELEASE=" "-DVCPKG_C_FLAGS_DEBUG=" " >>>> -DVCPKG_CRT_LINKAGE=dynamic" "-DVCPKG_LINKER_FLAGS=" " >>>> -DVCPKG_TARGET_ARCHITECTURE=x64" "-DCMAKE_INSTALL_LIBDIR:STRING=lib" " >>>> -DCMAKE_INSTALL_BINDIR:STRING=bin" "-G" "Ninja" " >>>> -DCMAKE_BUILD_TYPE=Release" "-DCMAKE_INSTALL_PREFIX=D:/dev/ >>>> vcpkg/packages/zlib_x64-windows"" >>>> FAILED: ../CMakeCache.txt >>>> cmd /c "cd .. && "D:/dev/vcpkg/downloads/tools/cmake-3.14.0 >>>> -windows/cmake-3.14.0-win32-x86/bin/cmake.exe" "D:/dev/ >>>> vcpkg/buildtrees/zlib/src/1.2.11-f690224aeb" "-DSKIP_INSTALL_FILES=ON" >>>> "-DSKIP_BUILD_EXAMPLES=ON" "-DCMAKE_MAKE_PROGRAM=C:/Program Files >>>> (x86)/Microsoft Visual Studio/2019 >>>> /Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" >>>> "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=D:/dev/ >>>> vcpkg/scripts/toolchains/windows.cmake" " >>>> -DVCPKG_TARGET_TRIPLET=x64-windows" "-DVCPKG_SET_CHARSET_FLAG=ON" " >>>> -DVCPKG_PLATFORM_TOOLSET=v142" "-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON" >>>> "-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON" " >>>> -DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON" " >>>> -DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE" " >>>> -DCMAKE_VERBOSE_MAKEFILE=ON" "-DVCPKG_APPLOCAL_DEPS=OFF" " >>>> -DCMAKE_TOOLCHAIN_FILE=D:/dev/vcpkg/scripts/buildsystems/vcpkg.cmake" " >>>> -DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON" "-DVCPKG_CXX_FLAGS=" >>>> "-DVCPKG_CXX_FLAGS_RELEASE=" "-DVCPKG_CXX_FLAGS_DEBUG=" " >>>> -DVCPKG_C_FLAGS=" "-DVCPKG_C_FLAGS_RELEASE=" "-DVCPKG_C_FLAGS_DEBUG=" " >>>> -DVCPKG_CRT_LINKAGE=dynamic" "-DVCPKG_LINKER_FLAGS=" " >>>> -DVCPKG_TARGET_ARCHITECTURE=x64" "-DCMAKE_INSTALL_LIBDIR:STRING=lib" " >>>> -DCMAKE_INSTALL_BINDIR:STRING=bin" "-G" "Ninja" " >>>> -DCMAKE_BUILD_TYPE=Release" "-DCMAKE_INSTALL_PREFIX=D:/dev/ >>>> vcpkg/packages/zlib_x64-windows"" >>>> CMake Error: The source >>>> "D:/dev/vcpkg/buildtrees/zlib/src/1.2.11-f690224aeb/CMakeLists.txt" >>>> does not match the source >>>> "D:/tmp/vcpkg/buildtrees/libjpeg-turbo/src/1.5.3-62cc34d993/CMakeLists.txt" >>>> used to generate cache. Re-run cmake with a different source >>>> directory. >>>> ninja: build stopped: subcommand failed. >>>> >>>> >>>> >>>> >>>> >>>> >>>> ------------------------------- >>>> Simon Björk >>>> Compositor/TD >>>> >>>> +46 (0)70-2859503 >>>> www.bjorkvisuals.com >>>> >>>> >>>> Den ons 18 dec. 2019 kl 16:49 skrev Chris Spence < >>>> ch...@digitaldevoid.com>: >>>> >>>>> Hi Simon, >>>>> >>>>> I’m certainly not fully qualified to answer, but I’m also in the >>>>> process of setting up OIIO on Windows 10, so I thought I’d chip in. >>>>> >>>>> 1. Use vcpkg. Is this working? Can it build with Python bindings/OCIO? >>>>> >>>>> Yes, Larry Gritz recommends using vcpkg. Unfortunately, some >>>>> dependencies are not available to vcpkg. >>>>> >>>>> On a another note, does the free version of Visual Studio (Community) >>>>> work with vcpkg/usd build club etc? >>>>> >>>>> Yes, Visual Studio Community works with vcpkg. >>>>> >>>>> If you’re building QT5, in addition to the Visual Studio Python & >>>>> Windows c++ desktop modules, instal ATL/MFC optional components (using >>>>> Visual Studio Installer). Otherwise after hours, & hours, & hours of >>>>> install you’ll likely get a build error (afxres.h missing). It may be a >>>>> good idea to install OpenCV to get the libtiff (& other libs) built: >>>>> https://cv-tricks.com/how-to/installation-of-opencv-4-1-0-in-windows-10-from-source/. >>>>> Please let me know if you come across a simpler solution to build libtiff >>>>> ver 3.9 > under Windows. >>>>> >>>>> Let me know how it goes, as half way through my OIIO ver 2.1 install, >>>>> my brand new laptop (HP OMEN 17” nVidia RTX 2060) had to be returned for >>>>> replacement due to hardware failures. >>>>> >>>>> >>>>> >>>>> Chris Spence >>>>> Digital Devoid, Inc. >>>>> 7300 Biscayne Blvd, Suite 405 >>>>> Miami, FL 33138 >>>>> >>>>> Tel: 305 757 1330 >>>>> >>>>> ch...@digitaldevoid.com >>>>> www.digitaldevoid.com >>>>> >>>>> On Dec 18, 2019, at 8:42 AM, Simon Björk <bjork.si...@gmail.com> >>>>> wrote: >>>>> >>>>> It's been a while since this was discussed so I thought I'd bring it >>>>> up again. >>>>> >>>>> What the currently best/easiest way to use OpenImageIO on Windows >>>>> (including python bindings)? >>>>> >>>>> Here's a few options I've found: >>>>> >>>>> 1. Use vcpkg. Is this working? Can it build with Python bindings/OCIO? >>>>> >>>>> 2. Use the USD build club <https://github.com/vfxpro99/usd-build-club>. >>>>> Is this still working? >>>>> >>>>> 3. Download pre-compiled sources from here >>>>> <https://www.lfd.uci.edu/~gohlke/pythonlibs/>. I'm not sure if all >>>>> cmd apps are available though, and python bindings are for Python 3. >>>>> >>>>> 4. Follow this >>>>> <http://jesnault.fr/website/how-to-build-windows-images-libraries/?lang=en> >>>>> guide. >>>>> I'm not sure if it's still relevant? The post is from 2015. >>>>> >>>>> On a another note, does the free version of Visual Studio (Community) >>>>> work with vcpkg/usd build club etc? >>>>> >>>>> Best regards, >>>>> Simon >>>>> >>>>> >>>>> ------------------------------- >>>>> Simon Björk >>>>> Compositor/TD >>>>> >>>>> +46 (0)70-2859503 >>>>> www.bjorkvisuals.com >>>>> _______________________________________________ >>>>> Oiio-dev mailing list >>>>> Oiio-dev@lists.openimageio.org >>>>> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org >>>>> >>>>> >>>>> _______________________________________________ >>>>> Oiio-dev mailing list >>>>> Oiio-dev@lists.openimageio.org >>>>> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org >>>>> >>>> >>>> _______________________________________________ >>>> Oiio-dev mailing >>>> listOiio-dev@lists.openimageio.orghttp://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org >>>> >>>> >>>> _______________________________________________ >>>> Oiio-dev mailing list >>>> Oiio-dev@lists.openimageio.org >>>> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org >>>> >>> _______________________________________________ >> Oiio-dev mailing list >> Oiio-dev@lists.openimageio.org >> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org >> >> >> _______________________________________________ >> Oiio-dev mailing list >> Oiio-dev@lists.openimageio.org >> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org >> > _______________________________________________ > Oiio-dev mailing list > Oiio-dev@lists.openimageio.org > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org > > _______________________________________________ > Oiio-dev mailing list > Oiio-dev@lists.openimageio.org > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org >
_______________________________________________ Oiio-dev mailing list Oiio-dev@lists.openimageio.org http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
