I get this error
6>D:\cycles..\lib\win64_vc15\openimageio\include\OpenImageIO/Imath.h(16,13): fatal error C1083: Cannot open include file: ‘Imath/ImathColor.h’: No such file or directory (compiling source file D:\cycles\src\subd\patch.cpp)
5>D:\cycles..\lib\win64_vc15\openimageio\include\OpenImageIO/Imath.h(16,13): fatal error C1083: Cannot open include file: ‘Imath/ImathColor.h’: No such file or directory (compiling source file D:\cycles\src\util\path.cpp)
7>Generating node_attribute.oso
6>D:\cycles..\lib\win64_vc15\openimageio\include\OpenImageIO/Imath.h(16,13): fatal error C1083: Cannot open include file: ‘Imath/ImathColor.h’: No such file or directory (compiling source file D:\cycles\src\subd\dice.cpp)
6>D:\cycles..\lib\win64_vc15\openimageio\include\OpenImageIO/Imath.h(16,13): fatal error C1083: Cannot open include file: ‘Imath/ImathColor.h’: No such file or directory (compiling source file D:\cycles\src\subd\split.cpp)
7>Generating node_background.oso
6>Done building project “cycles_subd.vcxproj” – FAILED.
There are many more like this. Any help would be greatly appreciated.
-Royce
You’re likely mixing master libs which are further ahead with cycles standalone which tends to lag a little, try grabbing one of the older tagged libs where imath still was included with openexr
The cycles repository master branch should build with the latest libraries, in fact it requires them. Generally running “make update” in the cycles repository should checkout the libraries with the appropriate version.
What can happen also is if you built a different cycles version earlier, the build configuration can be wrong for the new version. Removing the build folder and starting fresh is the easiest solution for that.
Actually, I just tried the master/3.10 and 3.20 libs with a clean build folder, and all have various issues, but none of them build, looks like it needs a little love. Taking a closer look…
Quit a bit was wrong, but i just pushed some fixes!
Release builds should work now, debug still has issues, as FindUSDPixar.cmake was unaware debug libs can exist and only looks for the release ones, but that’s a bit of a bigger fix than i have time for right now. @brecht do you want to pick this up? or should i? (won’t have time till after the 3.4 lib work)