I installed Android Studio and pressed two buttons in QT Creator:

Run a docker container:
export MY_IP=$(curl -s https://api.ipify.org)
sudo docker run -it --rm --cap-add=NET_ADMIN -p 1194:1194/udp -e HOST_ADDR=$MY_IP --name dockovpn alekslitvinenk/openvpn
or
sudo docker run -it --rm --cap-add=NET_ADMIN -p 1194:1194/udp -e HOST_ADDR=$MY_IP --name dockovpn alekslitvinenk/openvpn -v openvpn_conf:/opt/Dockovpn_data
to persist generated files in volume storage.
Type Ctrl+P then Ctrl+Q to turn interactive mode to daemon mode.
Determine its IP address:
sudo docker ps
sudo docker inspect dockovpn | grep IPAddress
I built BOOST with MSVC2022 in a similar way I built it with MSVC2017 except that I did install, but not stage:
cd C:\dev\repos\boost_1_80_0
set OPENSSL_ROOT_DIR=C:/dev/libs/OpenSSL
set OPENSSL_USE_STATIC_LIBS=ON
bootstrap.bat
b2 install --prefix=C:/dev/libs/boost_1_80_0 --toolset=msvc-14.3 link=static runtime-link=static variant=release address-model=64
b2 install --prefix=C:/dev/libs/boost_1_80_0 --toolset=msvc-14.3 link=static runtime-link=static variant=debug address-model=64
I am not sure if OPENSSL_ROOT_DIR takse an effect because boost::asio is header-only (but it depends on system and thread modules).
Install build tools, build OpenSSL as described in my previous post, extract QT sources with Bash:
tar -xf ../distrib/qt-everywhere-src-6.4.0.tar.xz
Configure QT as follows:
cd C:\dev\build\qt
"C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Auxiliary\Build\vcvarsall.bat" amd64
set "CMAKE_ROOT=C:\dev\PFiles\cmake-3.24.2-windows-x86_64\bin"
set "NINJA_ROOT=C:\dev\PFiles\ninja-win"
set "PERL_ROOT=C:\dev\PFiles\Strawberry\perl\bin"
set PATH=%CMAKE_ROOT%;%PATH%
set PATH=%NINJA_ROOT%;%PATH%
set PATH=%PERL_ROOT%;%PATH%
set PATH=C:\dev\PFiles\Python35;%PATH%
rem Check if the tools are in PATH
where perl.exe
where python.exe
where cmake.exe
where ninja.exe
set MY_INSTALL_PATH=C:/dev/libs/Qt6.4/windows
set MY_QT_SRC_DIR=C:\dev\repos\qt-everywhere-src-6.4.0
set CL=/MP
%MY_QT_SRC_DIR%\configure.bat -prefix %MY_INSTALL_PATH% -DQT_NO_EXCEPTIONS=1 -debug-and-release -force-debug-info -platform win32-msvc -opensource -confirm-license ^
-c++std c++20 -static -static-runtime -I "C:/Program Files/OpenSSL/include" -L "C:/Program Files/OpenSSL/lib" -openssl-linked ^
-skip qt3d -skip qt5compat -skip qtactiveqt -skip qtcharts -skip qtcoap -skip qtconnectivity ^
-skip qtdatavis3d -skip qtdoc -skip qtlottie -skip qtmqtt -skip qtnetworkauth -skip qtopcua ^
-skip qtserialport -skip qtpositioning -skip qtquicktimeline -skip qtquick3d -skip qtremoteobjects ^
-skip qtscxml -skip qtsensors -skip qtserialbus -skip qtvirtualkeyboard -skip qtwayland ^
-skip qtwebchannel -skip qtwebengine -skip qtwebview -skip qtquick3dphysics -skip qtspeech -skip qthttpserver
I built QT6.4. for MacOS first and then configured QT6.4 release build for iOS as follows:
export LC_ALL=en_US.UTF-8
export LANG=en_US.UTF-8
cd ~/build/qt
export MY_QT_SRC_DIR=~/repos/qt-everywhere-src-6.4.0
export MY_HOST_PATH=~/libs/QT6.4/MacOs
export MY_INSTALL_PATH=~/libs/QT6.4/iOs
export MY_MODE=release
${MY_QT_SRC_DIR}/configure -prefix $MY_INSTALL_PATH -qt-host-path $MY_HOST_PATH \
-platform macx-ios-clang -c++std c++20 -opensource -confirm-license \
-static -static-runtime -$MY_MODE -force-debug-info \
-no-openssl -securetransport -DQT_NO_EXCEPTIONS=1 \
-skip qt3d -skip qt5compat -skip qtactiveqt -skip qtcharts -skip qtcoap -skip qtconnectivity \
-skip qtdatavis3d -skip qtdoc -skip qtlottie -skip qtmqtt -skip qtnetworkauth -skip qtopcua \
-skip qtserialport -skip qtpositioning -skip qtquicktimeline -skip qtquick3d -skip qtremoteobjects \
-skip qtscxml -skip qtsensors -skip qtserialbus -skip qtvirtualkeyboard -skip qtwayland \
-skip qtwebchannel -skip qtwebengine -skip qtwebview -skip qtquick3dphysics -skip qtspeech -skip qtlocation \
-skip qthttpserver
I built QT6.4 and downloaded and installed QT Creator 8.0.1 and copied it to my MacOs machine:
scp qt-creator-opensource-mac-x86_64-8.0.1.dmg admin@192.168.0.112:/Users/admin/Downloads
QT Creator started successfully because I made .config folder writable while running my app with QT6.2. I added QT versions and kits:

I continued my experimentation in same SSH session where I built QT6.4 for MacOS with Ninja generator with the same QT sources location:
scp /mnt/d/dev.distrib/qt-everywhere-src-6.4.0.tar.xz admin@192.168.0.112:/Users/admin/repos
tar xf qt-everywhere-src-6.4.0.tar.xz
cd ~/build/qt
export MY_QT_SRC_DIR=~/repos/qt-everywhere-src-6.4.0
QT did not built with -debug-and-release option so I decided to build debug and release version separately with the following configurations: