building qt from sources - CMake Error at cmake/FindQt5.cmake

[kkoehne]

@GALAV , can you post the branch / version of Qt Creator that you are trying to build?

[GALAV]

@kkoehne
I cloned the highlighted URL

then I executed in the folder:

git submodule update --init --recursive 

[kkoehne]

So master branch ...

I assume you have checked that C:\Qt\6.3.1\msvc2019_64 contains a valid Qt 6 installation?

Can you re-run cmake with --trace argument, log this to a file and upload the dump somewhere to inspect? E.g.

del CMakeCache.txt && cmake --trace -DCMAKE_BUILD_TYPE=Debug -G Ninja -DCMAKE_PREFIX_PATH=C:\Qt\6.3.1\msvc2019_64 C:\Users\Administrator\Desktop\QT-CREATOR-SRC >trace.log 2>&1

[GALAV]

thanks for providing the command.

it seems i don't have the privileges to attach a log file.

[GALAV]

https://ctxt.io/2/AADgjVtcFw -- tracelog

[kkoehne]

CMake thinks the bitness of the Qt version does not match the bitness of the compiler. And indeed, it seems you're trying to build with the x86 compiler, but the Qt version you reference is 64bit.

If you indeed want to build an x86 binary, you most likely have to build Qt yourself. The installer only offers 64 bit binaries by default.

If choosing x86 was an accident, set up the build environment to 64 bit. For instance, launch cmd.exe and run

"C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Auxiliary\Build\vcvarsall.bat" amd64

[GalHA]

I am also running into the same error but on linux ubuntu 20.04

I have Qt 6.3.0 built and trying to build Qt Creator

[kkoehne]

@GalHA , Qt Creator master branch now expects Qt 6.2.

https://lists.qt-project.org/pipermail/qt-creator/2022-July/009050.html

So you need to install Qt 6.2 or newer.

[GalHA]

@kkoehne I have Qt 6.3.0 installed...

[GALAV]

@kkoehne
this :

"C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Auxiliary\Build\vcvarsall.bat" amd64

has fixed the problem for me, so thanks alot!
and regarding @GalHA 's problem, maybe the equivalent to linux with gcc might help

[kkoehne]

@GALAV , cool, then let's mark this thread as solved :)