Wiindows 10: "ninja : error : loading 'build.ninja'"

[scottmcdonnell]

wow this build process on Windows has me broken up.
Windows 10 using the 'Visual Studio 17 2022' generator (same result in 2019).
I've made it through the setup and bootstrap. For that I would suggest some checks in vscmds.sh that ENV variables set point to directories that exist and have expected subdirectories.

I am failing with 10 errors now:

• ninja : error : loading 'build.ninja': The system cannot find the file specified. [E:\dev\OpenRV_build\cmake\dependencies\RV_DEPS_SPDLOG.vcxproj]
• ninja : error : loading 'build.ninja': The system cannot find the file specified. [E:\dev\OpenRV_build\cmake\dependencies\RV_DEPS_IMATH.vcxproj]
• ninja : error : loading 'build.ninja': The system cannot find the file specified. [E:\dev\OpenRV_build\cmake\dependencies\RV_DEPS_ZLIB.vcxproj]
• ninja : error : loading 'build.ninja': The system cannot find the file specified. [E:\dev\OpenRV_build\cmake\dependencies\RV_DEPS_ZLIB.vcxproj]
• ninja : error : loading 'build.ninja': The system cannot find the file specified. [E:\dev\OpenRV_build\cmake\dependencies\RV_DEPS_JPEGTURBO.vcxproj]
• CUSTOMBUILD : error : pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts. [E:\dev\OpenRV_build\cmake\dependencies\RV_DEPS_PYTHON3-stage-target.vcxproj]

From the docs it says that Cmake should be the msys one and point to Ninja.

in cmd.exe

where cmake
> E:\dev-tools\msys2\mingw64\bin\cmake.exe
> E:\dev-tools\Strawberry\c\bin\cmake.exe

and cmake --help does return *Ninja as the default generator

in MSYS MNGW64 console:

where cmake
> E:\dev-tools\msys2\mingw64\bin\cmake.exe

and cmake --help shows *Visual Studio 17 2022 as the default generator not Ninja - but that is because the environment variable CMAKE_GENERATOR="Visual Studio 17 2022" set using rvcmds.sh.

How can I test if Ninja is set up correctly? Any steps I can take to progress?

[scottmcdonnell]

To answer my own question - I was setting the rvcmds.sh variables using the suggested export as environmental variables export CMAKE_GENERATOR="Visual Studio 16 2019" rather than editing the values in rvcmds.sh directly.

By doing this the environmental variable CMAKE_GENERATOR is set for CMAKE as well breaking the build process. I would suggest changing the variables to be namespaced to avoid the conflict RV_CMAKE_GENERATOR in rvcmds.exe as CMAKE_GENERATOR must remain as "Ninja" for the build process to work.