building 6.9.2 and 6.9.1 fails to find file for installation

[Nuno Pedrosa]

I am trying to build Qt from the sources in download.qt.io in the official_releases
I have tried 6.9.1 and 6.9.2, but I keep having the same problem.

here are my settings:
python 3.9.13
cmake 4.1.1
Visual studio 2022 17.14.13

it seems to satisfy the minimum requirements.

here the list of commands I use:

set QT_VERS=6.9.1
mkdir msvc2022_x64
cd msvc2022_x64
call "C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Auxiliary\Build\vcvarsall.bat" amd64
path=%cd%\qtbase\bin;%path%
call ..\qt-everywhere-src-%QT_VERS%\configure.bat --prefix=C:\kbcdev\qt\%QT_VERS%_MY\msvc2022_x64 -opensource -confirm-license -debug-and-release -nomake tests -nomake examples -qtlibinfix _my -- -DCMAKE_C_COMPILER=cl.exe -DCMAKE_CXX_COMPILER=cl.exe || goto :errors
cmake --build . --config Debug || goto :errors
cmake --install . --config Debug || goto :errors

it compiles fine (I think) and when running the install step I get this:

CMake Error at qtdeclarative/tools/qmltime/cmake_install.cmake:80 (file):
  file INSTALL cannot find
  "C:/qt_build/6.9.1/msvc2022_x64/qtbase/qml/QmlTime/qmltime.qmltypes": File
  exists.
Call Stack (most recent call first):
  qtdeclarative/tools/cmake_install.cmake:102 (include)
  qtdeclarative/cmake_install.cmake:47 (include)
  cmake_install.cmake:67 (include)

has anybody come across this problem?

I am quite familiar with cmake, but this is a massive project and I could not find where this files was supposed to be generated to try and fix that.

Thanks

[kkoehne]

Shot in the dark, but you might try a slightly older CMake version. Just suggesting this as CMake 4.1.1 is fairly new, and the error message looks ... dubious.

[Nuno Pedrosa]

thanks for the suggestion. switching to cmake 3.22.6, which is the minimum recommended, I get the same problem exactly.
I even tried the 6.9.2 branch from git, but got the same result.
I will be having a go with 6.10 RC to see if I have the same issue.

[Nuno Pedrosa]

After many tries I tracked it down to the type of configuration if I use debug-release, which creates a Ninja Multiconfig project, it fails with this error.
but if I build debug and release version is separated directories it works fine.

hopefully this finding will help others.