Building project with Qt6

[DSCaskey]

Build Environment
Windows 11

Visual Studio 2022 Community
Visual Studio SDK

Qt Creator 10.0.2
Kit : Desktop Qt 6.2.4 MSVC 2019 64bit
Qt version: c::\Qt\6.2.4\msvc2019_64\bin\qmake.exe

qmake: C:/Qt/6.2.4/msvc2019_64/bin/qmake.exe D:\Github\Seamly2D\Seamly2D.pro -spec win32-msvc "CONFIG+=qtquickcompiler" && C:/Qt/Tools/QtCreator/bin/jom/jom.exe qmake_all

Make: jom.exe in D:\Github\build-Seamly2D-Qt6_64bit-Release

Added to system envirnonment:
INCLUDE
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.36.32532\include
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.36.32532\ATLMFC\include
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\VS\include
C:\Program Files (x86)\Windows Kits\10\Include\10.0.22621.0\um
C:\Program Files (x86)\Windows Kits\10\Include\10.0.22621.0\shared
C:\Program Files (x86)\Windows Kits\10\Include\10.0.22621.0\ucrt

LIB
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.36.32532\ATLMFC\lib\x64
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.36.32532\lib\x64
C:\Qt\6.2.4\msvc2019_64\include
C:\Program Files (x86)\Windows Kits\10\Lib\10.0.22621.0\um\x64
C:\Program Files (x86)\Windows Kits\10\Lib\10.0.22621.0\ucrt\x64

PATH
C:\Qt\6.2.4\msvc2019_64\bin
C:\Qt\6.2.4\msvc2019_64\bin\Debug
C:\Program Files (x86)\Windows Kits\10\bin\10.0.22621.0\x64

QMKSPEC
C:\Qt\6.2.4\msvc2019_64\mkspecs\win32-msvc // No additional warning flags set

Needs the #include in ifcdef.cpp.
Compiles without error or a single warning - same as with Qt5.
Build runs from a clean install, but has issues running with an existing settings ini file.
Build also has other issues to resolve.

Added the -Aall flag, and I stopped building after the compiler hit over 17, 000 warnings - most of which were directed at the MSVC libs, and appeared to be more of commentary on compiler optimizations.

Don't know (yet) what other flags may be turned on to produce the warnings in #981

[DSCaskey]

The warnings outlined in issue #981 are triggered by setting the debugger with the MSVC windows kit:

C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\cdb.exe