Error on Qt 6 Building from source for Windows Based

Chris Kawa

@NiVa99 The bat is explicitly for msvc. Your errors seem to come from using clang without environment set up for it. The path has msvc2019_64 in it and your build errors are from gcc/mingw.

You seem to have completely mixed up environment for those three different compilers. Which one do you actually want to use - msvc, clang or gcc/mingw ?

Notice that directory C:/Qt/6.2.2/Build disappear at this moment building.

Well yeah, because it's a temporary build directory and the bat removes it after the install: rmdir %BUILD_DIR% /Q /S. If you want it to stay just modify the bat and remove or comment out that line.

NiVa99

I have succeeded to build Qt6.2.2 for arch amd64 and x64 with this following bat.
But interested in to build with mingw too

:: x64 amd64 x86
SET ARCH=x86


:: SET VS_ENVIRONMENT="C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Auxiliary\Build\vcvars64.bat"
SET VS_ENVIRONMENT="C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Auxiliary\Build\vcvarsall.bat %ARCH%"
CALL %VS_ENVIRONMENT%

SET SRC_DIR="d:\Logiciels\Qt\6.2.2\Src"
SET BUILD_DIR="d:\Logiciels\Qt\6.2.2\Build"
SET INSTALL_DIR="C:\release-vs2019-%ARCH%"
SET CONFIGURE_OPTIONS=-debug-and-release -mp -opensource -confirm-license

call %VS_ENVIRONMENT%
mkdir %BUILD_DIR%
mkdir %INSTALL_DIR%
cd %BUILD_DIR%
call %SRC_DIR%\configure -prefix %INSTALL_DIR% %CONFIGURE_OPTIONS%
cmake --build . --parallel
cmake --install .
cd %INSTALL_DIR%
rmdir %BUILD_DIR% /Q /S
pause

Chris Kawa

For mingw don't call the msvc bat to setup environment. I don't know if mingw has a handy bat to set it up for you, but if not then just do it manually by adding the relevant paths to bin, include and lib directories. Something like this

SET PATH=%PATH%;C:\mingw\bin
SET CPLUS_INCLUDE_PATH=C:\mingw\include
SET LIBRARY_PATH=C:\mingw\lib

substituting the paths to your actual mingw installation directories.

NiVa99

Thank you, I have removed rmdir line and I will try mingw build.

Just staying on msvc build, I have just one architecture x86 that does not build either than amd64 dll seeing it with Dependencies.

d:\Logiciels\Qt\6.2.2>SET VS_ENVIRONMENT="C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Auxiliary\Build\vcvarsall.bat x86"

d:\Logiciels\Qt\6.2.2>"C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Auxiliary\Build\vcvarsall.bat x86"
'"C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Auxiliary\Build\vcvarsall.bat x86"' n’est pas reconnu en tant que commande interne
ou externe, un programme exécutable ou un fichier de commandes.

d:\Logiciels\Qt\6.2.2>SET SRC_DIR="d:\Logiciels\Qt\6.2.2\Src"

d:\Logiciels\Qt\6.2.2>SET BUILD_DIR="d:\Logiciels\Qt\6.2.2\Build"

d:\Logiciels\Qt\6.2.2>SET INSTALL_DIR="C:\release-vs2019-x86"

d:\Logiciels\Qt\6.2.2>SET CONFIGURE_OPTIONS=-debug-and-release -mp -opensource -confirm-license

d:\Logiciels\Qt\6.2.2>call "C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Auxiliary\Build\vcvarsall.bat x86"
'"C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Auxiliary\Build\vcvarsall.bat x86"' n’est pas reconnu en tant que commande interne
ou externe, un programme exécutable ou un fichier de commandes.

d:\Logiciels\Qt\6.2.2>mkdir "d:\Logiciels\Qt\6.2.2\Build"
Un sous-répertoire ou un fichier d:\Logiciels\Qt\6.2.2\Build existe déjà.

d:\Logiciels\Qt\6.2.2>mkdir "C:\release-vs2019-x86"
Un sous-répertoire ou un fichier C:\release-vs2019-x86 existe déjà.

d:\Logiciels\Qt\6.2.2>cd "d:\Logiciels\Qt\6.2.2\Build"

d:\Logiciels\Qt\6.2.2\Build>call "d:\Logiciels\Qt\6.2.2\Src"\configure -prefix "C:\release-vs2019-x86" -debug-and-release -mp -opensource -confirm-license
+ cd qtbase
+ d:\Logiciels\Qt\6.2.2\src\qtbase\configure.bat -top-level -prefix "C:\release-vs2019-x86" -debug-and-release -mp -opensource -confirm-license

Chris Kawa

'"C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Auxiliary\Build\vcvarsall.bat x86"' n’est pas reconnu en tant que commande interne
ou externe, un programme exécutable ou un fichier de commandes.

Don't put x86 in the quotes because it treats vcvarsall.bat x86 as a file name with space. Put the parameter outside of the quotes. It's the same for all architectures. You can also just use vcvars32.bat without any parameters, which does the same.

NiVa99

I am trying this version of bat.

:: x64 amd64 x86

:: SET VS_ENVIRONMENT="C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Auxiliary\Build\vcvars64.bat"
SET ARCH=x86
:: SET VS_ENVIRONMENT="C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Auxiliary\Build\vcvarsall.bat %ARCH%"

SET VS_ENVIRONMENT="C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Auxiliary\Build\vcvars32.bat"
CALL %VS_ENVIRONMENT%

SET SRC_DIR="d:\Logiciels\Qt\6.2.2\Src"
SET BUILD_DIR="d:\Logiciels\Qt\6.2.2\Build"
SET INSTALL_DIR="d:\Qt-6.2.2-release-vs2019-%ARCH%"
SET CONFIGURE_OPTIONS=-debug-and-release -mp -opensource -confirm-license

mkdir %BUILD_DIR%
mkdir %INSTALL_DIR%
cd %BUILD_DIR%
CALL %SRC_DIR%\configure -prefix %INSTALL_DIR% %CONFIGURE_OPTIONS%
cmake --build . --parallel 4
cmake --install .
:: cd %INSTALL_DIR%
:: rmdir %BUILD_DIR% /Q /S
pause

which cause errors

Performing C++ SOURCE FILE Test HAVE_WIN10_WIN32_WINNT failed with the following output:
Change Dir: D:/Logiciels/Qt/6.2.2/Build/CMakeFiles/CMakeTmp

Run Build Command(s):C:/ninja-win/ninja.exe -f build-Release.ninja cmTC_4e432 && [1/2] Building CXX object CMakeFiles/cmTC_4e432.dir/Release/src.cxx.obj

**FAILED**: CMakeFiles/cmTC_4e432.dir/Release/src.cxx.obj 

C:\Strawberry\c\bin\c++.exe -DHAVE_WIN10_WIN32_WINNT -DCMAKE_INTDIR=\"Release\"  -O3 -DNDEBUG -std=gnu++17 -o CMakeFiles/cmTC_4e432.dir/Release/src.cxx.obj -c D:/Logiciels/Qt/6.2.2/Build/CMakeFiles/CMakeTmp/src.cxx

D:/Logiciels/Qt/6.2.2/Build/CMakeFiles/CMakeTmp/src.cxx:6:10: error: #error "_WIN32_WINNT version too low"
         #error "_WIN32_WINNT version too low"
          ^~~~~
D:/Logiciels/Qt/6.2.2/Build/CMakeFiles/CMakeTmp/src.cxx:9:10: error: #error "WINVER version too low"
         #error "WINVER version too low"
          ^~~~~
ninja: build stopped: subcommand failed.



Source file was:
        #include <windows.h>
        #if !defined(_WIN32_WINNT) && !defined(WINVER)
        #error "_WIN32_WINNT and WINVER are not defined"
        #endif
        #if defined(_WIN32_WINNT) && (_WIN32_WINNT < 0x0A00)
        #error "_WIN32_WINNT version too low"
        #endif
        #if defined(WINVER) && (WINVER < 0x0A00)
        #error "WINVER version too low"
        #endif
        int main() { return 0; }
    
Performing C++ SOURCE FILE Test TEST_use_lld_linker failed with the following output:
Change Dir: D:/Logiciels/Qt/6.2.2/Build/CMakeFiles/CMakeTmp

Run Build Command(s):C:/ninja-win/ninja.exe -f build-Release.ninja cmTC_01c1b && [1/2] Building CXX object CMakeFiles/cmTC_01c1b.dir/Release/src.cxx.obj

**FAILED**: CMakeFiles/cmTC_01c1b.dir/Release/src.cxx.obj 

C:\Strawberry\c\bin\c++.exe -DTEST_use_lld_linker -DCMAKE_INTDIR=\"Release\"  -O3 -DNDEBUG   -fuse-ld=lld -std=gnu++17 -o CMakeFiles/cmTC_01c1b.dir/Release/src.cxx.obj -c D:/Logiciels/Qt/6.2.2/Build/CMakeFiles/CMakeTmp/src.cxx

c++.exe: error: unrecognized command line option '-fuse-ld=lld'; did you mean '-fuse-ld=bfd'?
ninja: build stopped: subcommand failed.



Source file was:
int main() { return 0; }
Performing C++ SOURCE FILE Test TEST_enable_new_dtags failed with the following output:
Change Dir: D:/Logiciels/Qt/6.2.2/Build/CMakeFiles/CMakeTmp

Run Build Command(s):C:/ninja-win/ninja.exe -f build-Release.ninja cmTC_ea62a && [1/2] Building CXX object CMakeFiles/cmTC_ea62a.dir/Release/src.cxx.obj

[2/2] Linking CXX executable Release\cmTC_ea62a.exe

FAILED: Release/cmTC_ea62a.exe 

cmd.exe /C "cd . && C:\Strawberry\c\bin\c++.exe -O3 -DNDEBUG -Wl,--enable-new-dtags CMakeFiles/cmTC_ea62a.dir/Release/src.cxx.obj -o Release\cmTC_ea62a.exe -Wl,--out-implib,Release\libcmTC_ea62a.dll.a -Wl,--major-image-version,0,--minor-image-version,0  -lkernel32 -luser32 -lgdi32 -lwinspool -lshell32 -lole32 -loleaut32 -luuid -lcomdlg32 -ladvapi32 && cd ."

C:/Strawberry/c/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../x86_64-w64-mingw32/bin/ld.exe: unrecognized option '--enable-new-dtags'

C:/Strawberry/c/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../x86_64-w64-mingw32/bin/ld.exe: use the --help option for usage information

collect2.exe: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.

Chris Kawa

The error tells you what's wrong. Mingw sets _WIN32_WINNT and WINVER too low. I think Windows XP is its default and Qt6 requires at least Windows 10, so add defines for the appropriate versions in the configure params. Here are the values: WINVER and _WIN32_WINNT.

NiVa99

This post is deleted!

NiVa99

This post is deleted!

NiVa99

This post is deleted!

Christian Ehrlicher

Do you want to compile with MinGW or MSVC?
If MinGW - why do you call MSVC batch files which set MSVC specific env vars?
If MSVC - why do you call g++?

NiVa99

First want to call msvc VS2019 building arch amd64 x64 (done) and x86.
Second doing same build with mingw last as documented. link text

Christian Ehrlicher

Still does not explain why you set MSVC env vars when trying to build with MinGW.

NiVa99

Tyying this batch inspired from this post. I thank Chris Kawa.

I thought it was to build with MSVC 2019.

SET VS_ENVIRONMENT="c:\Program Files (x86)\Microsoft Visual Studio\2019\VC\Auxiliary\Build\vcvars64.bat"
SET SRC_DIR="d:\Logiciels\Qt\6.2.2\Src"
SET BUILD_DIR="d:\Logiciels\Qt\6.2.2\Build"
SET INSTALL_DIR="d:\Logiciels\Qt\6.2.2\vs2019-x64"
SET CONFIGURE_OPTIONS=-debug-and-release -mp -opensource -confirm-license

call %VS_ENVIRONMENT%
mkdir %BUILD_DIR%
mkdir %INSTALL_DIR%
cd %BUILD_DIR%
call %SRC_DIR%\configure -prefix %INSTALL_DIR% %CONFIGURE_OPTIONS%
cmake --build . --parallel
cmake --install .
cmake --install . --config Release
cd %INSTALL_DIR%
:: rmdir %BUILD_DIR% /Q /S
pause

I got these error, have to set WINVER and _WIN32_WINNT defines but how doing it ?

Performing C++ SOURCE FILE Test HAVE_WIN10_WIN32_WINNT failed with the following output:
Change Dir: D:/Logiciels/Qt/6.2.2/Build/CMakeFiles/CMakeTmp

Run Build Command(s):C:/ninja-win/ninja.exe -f build-Release.ninja cmTC_9e6d0 && [1/2] Building CXX object CMakeFiles/cmTC_9e6d0.dir/Release/src.cxx.obj

FAILED: CMakeFiles/cmTC_9e6d0.dir/Release/src.cxx.obj 

C:\Strawberry\c\bin\c++.exe -DHAVE_WIN10_WIN32_WINNT -DCMAKE_INTDIR=\"Release\"  -O3 -DNDEBUG -std=gnu++17 -o CMakeFiles/cmTC_9e6d0.dir/Release/src.cxx.obj -c D:/Logiciels/Qt/6.2.2/Build/CMakeFiles/CMakeTmp/src.cxx

D:/Logiciels/Qt/6.2.2/Build/CMakeFiles/CMakeTmp/src.cxx:6:10: error: #error "_WIN32_WINNT version **too low**"
         #error "_WIN32_WINNT version too low"
          ^~~~~
D:/Logiciels/Qt/6.2.2/Build/CMakeFiles/CMakeTmp/src.cxx:9:10: error: #error "WINVER version too low"
         #error "WINVER version too low"
          ^~~~~
ninja: build stopped: subcommand failed.

microsoft modifying-winver-and-win32-winnt
#define WINVER 0x0A00
#define _WIN32_WINNT 0x0A00

Do I have to modify CMakeLists.txt or is it possibe to pass these defines from batch ?
Thank you

NiVa99

@Chris-Kawa

So I understood but don't know where can i add those defines'param for a build MSVC, in the bat or in cmakelists.txt or ninja config ?

post

Thank you.

NiVa99

It seems that it is well defined in qtbase\mkspecs\features\qt_module.prf|349| DEFINES *= _WIN32_WINNT=0x0A00

Why only in this file ?

Chris Kawa

@NiVa99 said:

So I understood but don't know where can i add those defines'param for a build MSVC, in the bat or in cmakelists.txt or ninja config ?

Sorry, but I'm completely confused now which build you're talking about. You're constantly mixing msvc, mingw and now ninja and I can't understand which errors you're getting from which build.

Could you maybe focus on one and state clearly which is it?
And don't modify any Qt files.

NiVa99

Building according to this note Building Qt 6 from sources
Requirements are CMake, Ninja, Perl, Python.

Build Qt from Sources I search for is doing it with MSVC 2019, VS2022 (and later Ming).

kkoehne

@NiVa99 said in Error on Qt 6 Building from source for Windows Based:

C:\Strawberry\c\bin\c++.exe

Remove C:\Strawberry\c\bin from your PATH environment variable, and try a clean build again.

Background: CMake prefers clang/gcc over MSVC, even on Windows. So if you have anything called clang.exe, c++.exe ... in your PATH cmake will try to use that for compilation. Anyhow, the binaries in C:\Strawberry\c\bin are only for internal use of Strawberry - at least they're not enough to compile Qt.

If you want to use MSVC, call vcvars64.bat like @Christian-Ehrlicher suggested. If you want to use MinGW, prefer one of the MinGW toolchains that are supported by Qt: https://wiki.qt.io/MinGW

NiVa99

This post is deleted!