But when I uncheck Build Tools -> MinGW 13.1 64-bit it try to delete whole Qt:

According to the Qt Online Installer's package manager, "Qt 6.12.0" > "MinGW 13.1.0 64-bit" depends on "Build Tools" > "MinGW 13.1.0 64-bit". So if you uninstall the compiler, it will also uninstall the libraries.

This is not a bug. It also works the other way round: When someone tries to install "Qt 6.12.0" > "MinGW 13.1.0 64-bit", the installer will automatically install "Build Tools" > "MinGW 13.1.0 64-bit" too.

P.S. I want to delete MinGW 13.1 64-bit because I recognized that I can use MinGW GCC 16.2 from https://winlibs.com/ with Qt because I have built a lot of libraries with GCC 16.2 and I do not want to rebuild them with GCC 13.1

You can use your MinGW 16.2 toolchain to build Qt from source: https://doc.qt.io/qt-6/windows-building.html This will have no dependency on MinGW 13.1.

It would make sense if the "Build Tools" > "MinGW 13.1.0 64-bit" checkbox were automatically selected when the "Qt 6.12.0" > "MinGW 13.1.0 64-bit" checkbox appeared. Otherwise, it seems that the "Build Tools" > "MinGW 13.1.0 64-bit" option is independent of the "Qt 6.12.0" > "MinGW 13.1.0 64-bit" option. We can only find out about this at the final step.

I agree.

Would you be willing to submit a change request to https://qt-project.atlassian.net/ ?

@8Observer8 said in Unable to delete "MinGW 13.1 64-bit" from "Build Tools":

@JKSH said in Unable to delete "MinGW 13.1 64-bit" from "Build Tools":

You can use your MinGW 16.2 toolchain to build Qt from source: https://doc.qt.io/qt-6/windows-building.html This will have no dependency on MinGW 13.1.

It looks I should because of ABI.

Indeed.

Thank you for sharing your findings/solutions.

Would rather formulate it as: if you want to keep you application code private, you have to provide the build artifacts that allows your users to relink the application with their own Qt library.

If you distribute a statically built Qt .exe under the free LGPLv3 license, you must choose one of two options:

1. Make your project open source and share your full source code.
2. Keep your source code private, but provide your compiled .obj files so users can relink the application with their own Qt library.

You can use your MinGW 16.2 toolchain to build Qt from source: https://doc.qt.io/qt-6/windows-building.html This will have no dependency on MinGW 13.1.

Thank you very much! It is the best solution for my main goal! The main goal was to use Qt with MinGW GCC 16.2.0 from WinLibs.

I've saved my result here because it can be useful for someone or for me in the Future. I've built Qt 6.12.0 statically for Windows 10 with MinGW 16.2 for OpenGL and Desktop only. The instruction below was made by free Gemini 3.8 Flash but I have tested it.

The result:

• C:\Qt\6.12.0_static_mingw162 - 496 MB
• 2 minutes to clone source
• 20 minutes to build
• 2 seconds to install
• Released stripped EXE - 30 MB (12 MB in archive) for the OpenGL project: https://github.com/ivan-enzhaev/OpenGLTestQt6
  

I have downloaded Qt Creator here: https://github.com/qt-creator/qt-creator/releases

The step-by-step guide:

• Download and unzip MinGW GCC 16.2.0: https://winlibs.com/ (add the C:\mingw64_16.2\bin path to Environment Variables
• Download and install CMake: https://cmake.org/download/
• Download and install Ninja (WinLibs is included it)

The following guide was generated by free Gemini 3.8 Flash (in Google AI Studio) but they were tested by me:

Because you only need Desktop OpenGL, QWindow, and QtWidgets, you do not even need the umbrella Qt repository or Perl. Everything you need is inside qtbase!

Cloning only qtbase is faster, uses very little disk space, and takes only ~15 to 25 minutes to build on your i7-7700.

Step 1: Clone only qtbase

Open a command prompt (make sure git, cmake, ninja, and WinLibs GCC bin are in your PATH):

mkdir C:\QtSource
cd C:\QtSource

:: Clone only qtbase (shallow clone, ~150 MB download)
git clone --depth 1 -b v6.12.0 https://code.qt.io/qt/qtbase.git

Step 2: Configure for a Static Build

Create a separate build folder and run configure.bat:

mkdir C:\QtBuild
cd C:\QtBuild

:: Run configure from qtbase
C:\QtSource\qtbase\configure.bat ^
  -static ^
  -release ^
  -prefix C:\Qt\6.12.0_static_mingw162 ^
  -opengl desktop ^
  -nomake examples ^
  -nomake tests

What these flags do:

• -static: Compiles all Qt libraries as static archives (.a) instead of dynamic DLLs (.dll).
• -release: Compiles optimized release libraries without bulky debug symbols (drastically cuts compile time and disk space).
• -opengl desktop: Uses native desktop OpenGL (opengl32.lib / GLES wrapper).
• -nomake examples -nomake tests: Skips all sample apps and unit tests to save 10+ minutes of build time.

Step 3: Compile and Install

Run ninja (it will automatically use all 8 threads of your i7-7700):

ninja
ninja install

• Estimated Time: ~15 to 25 minutes.
• Final Installed Size: Only ~450 – 650 MB in C:\Qt\6.12.0_static_mingw162.
• Once ninja install completes, you can delete C:\QtBuild and C:\QtSource to reclaim disk space.

Step 4: Register Kit in Qt Creator

1. Open Qt Creator.
2. Go to Edit → Preferences (or Tools → Options).
3. Under Kits → Qt Versions, click Add and choose:
   C:\Qt\6.12.0_static_mingw162\bin\qmake.exe
4. Under Kits → Compilers, verify your WinLibs GCC 16.2 (C and C++) is detected.
5. Under Kits → Debuggers, click Add:
   • Name: GDB (WinLibs MinGW 16.2)
   • Path: Choose gdb.exe from your WinLibs directory (e.g. C:\winlibs-...\bin\gdb.exe).
6. Under Kits → Kits, click Add:
   • Name: Qt 6.12.0 Static (MinGW 16.2)
   • Compiler: WinLibs GCC 16.2 (C and C++)
   • Debugger: GDB (WinLibs MinGW 16.2)
   • Qt version: The static one you just added.
   • CMake Generator: Ninja

Step 5: How to use it in your project's CMakeLists.txt

When using a static Qt build on Windows, Qt's CMake macros automatically link the static platform plugin (qwindows.lib / libqwindows.a).

To make your application a single, 100% standalone .exe with no external DLLs needed, add -static to your target link options:

cmake_minimum_required(VERSION 3.21)
project(OpenGLTestQt6 LANGUAGES CXX)

set(CMAKE_CXX_STANDARD 20)
set(CMAKE_CXX_STANDARD_REQUIRED ON)

set(CMAKE_AUTOMOC ON)
set(CMAKE_AUTOUIC ON)

find_package(Qt6 COMPONENTS Widgets OpenGLWidgets REQUIRED)

add_executable(OpenGLTest WIN32
    main.cpp
    mainwindow.cpp
    mainwindow.h
    mainwindow.ui
)

target_link_libraries(OpenGLTest PRIVATE
    Qt6::Widgets
    Qt6::OpenGLWidgets
    opengl32
)

if(MINGW)
    target_link_options(OpenGLTest PRIVATE
        -static
        $<$<CONFIG:Release>:-s>
    )
endif()

Your resulting .exe will launch independently on any Windows machine with zero DLL dependencies.

You can use your MinGW 16.2 toolchain to build Qt from source: https://doc.qt.io/qt-6/windows-building.html This will have no dependency on MinGW 13.1.

It looks I should because of ABI. The free Gemini 3.8 Flash says: Benefit: 100% ABI compatibility, matching runtimes, and no mysterious linker or runtime crashes. Thus, mixing Qt MinGW 13.1 with MinGW 16.2 (build tools) may be the cause of crashes.

When someone tries to install "Qt 6.12.0" > "MinGW 13.1.0 64-bit", the installer will automatically install "Build Tools" > "MinGW 13.1.0 64-bit" too.

I've uninstalled Qt with Revo Uninstaller Pro to delete all files completely to install it again. When I check "Qt 6.12.0" > "MinGW 13.1.0 64-bit" the installer does not check "Build Tools" > "MinGW 13.1.0 64-bit" automatically:

So it seems that it is possible to install Qt without "Build Tools" > "MinGW 13.1.0 64-bit". But on the end step it includes "Build Tools" > "MinGW 13.1.0 64-bit":

It would make sense if the "Build Tools" > "MinGW 13.1.0 64-bit" checkbox were automatically selected when the "Qt 6.12.0" > "MinGW 13.1.0 64-bit" checkbox appeared. Otherwise, it seems that the "Build Tools" > "MinGW 13.1.0 64-bit" option is independent of the "Qt 6.12.0" > "MinGW 13.1.0 64-bit" option. We can only find out about this at the final step.

But when I uncheck Build Tools -> MinGW 13.1 64-bit it try to delete whole Qt:

According to the Qt Online Installer's package manager, "Qt 6.12.0" > "MinGW 13.1.0 64-bit" depends on "Build Tools" > "MinGW 13.1.0 64-bit". So if you uninstall the compiler, it will also uninstall the libraries.

This is not a bug. It also works the other way round: When someone tries to install "Qt 6.12.0" > "MinGW 13.1.0 64-bit", the installer will automatically install "Build Tools" > "MinGW 13.1.0 64-bit" too.

P.S. I want to delete MinGW 13.1 64-bit because I recognized that I can use MinGW GCC 16.2 from https://winlibs.com/ with Qt because I have built a lot of libraries with GCC 16.2 and I do not want to rebuild them with GCC 13.1

You can use your MinGW 16.2 toolchain to build Qt from source: https://doc.qt.io/qt-6/windows-building.html This will have no dependency on MinGW 13.1.