Qt Creator: cmake errors after downgrade of MSVC compiler

Asperamanca

I tried downgrading MSVC after severe debugging issues. After that, I manually re-detected compilers in Qt Creator.
Now, when I try to configure cmake for a debug build ("Re-configure with initial parameters") even with a small test project, I get

CMake Error at _hipase/cmake/modules/HIPASE.cmake:107 (find_package):
  By not providing "FindQt6.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "Qt6", but
  CMake did not find one.

  Could not find a package configuration file provided by "Qt6" with any of
  the following names:

    Qt6Config.cmake
    qt6-config.cmake

  Add the installation prefix of "Qt6" to CMAKE_PREFIX_PATH or set "Qt6_DIR"
  to a directory containing one of the above files.  If "Qt6" provides a
  separate development package or SDK, be sure it has been installed.

As per https://stackoverflow.com/questions/71086422/cmake-cannot-find-packages-within-qt6-installation I tried manually setting the Qt6 dir (although that somehow defeats the purpose of Kits, no?), by providing this additional Cmake option:

"-DQt6_DIR=q:/Qt/6.8.2/msvc2022_64/lib/cmake/Qt6"

But no change.
Any suggestions?

Asperamanca

Well, after re-upgrading again, cmake works, but I did the downgrade for a reason.
So a solution would be greatly appreciated.

Christian Ehrlicher

What msvc version do you use?

Asperamanca

@Christian-Ehrlicher Now back to 19.44.35211 (Visual Studio 2022 17.14.8)

Asperamanca

Strangely, the kits in Qt Creator detect it as 17.9.34622.214
But I was always more than confused with Microsoft's version scheme(s)

Christian Ehrlicher

17.9 should also work. Make sure to start with a clean build dir and also no CMakeLists.txt.user in the source tree

Asperamanca

@Christian-Ehrlicher said in Qt Creator: cmake errors after downgrade of MSVC compiler:

17.9 should also work. Make sure to start with a clean build dir and also no CMakeLists.txt.user in the source tree

I did everything, but forgot about .txt.user
Will try that...

EDIT:
However, after the torturous downgrade/upgrade experience, my VS debugger decided to behave, so I'll keep you advice for the future.