aqt is a tool that can be used to install Qt, modules, tools related to Qt,
source, docs, and examples, available at https://download.qt.io/.
aqt, you will need to tell
aqt exactly what you want it
to install. This section of the documentation is meant to walk you through the
process of finding out what packages are available to
aqt, so you can tell
aqt what you want to install.
Please note that every
aqt subcommand has a
--help option; please use
it if you are having trouble!
General usage of
aqt looks like this:
aqt install-qt <host> <target> (<Qt version> | <spec>) [<arch>]
If you have installed
aqt with pip, you can run it with the command script
but in some cases you may need to run it as
python -m aqt.
Some older operating systems may require you to specify Python version 3, like this:
python3 -m aqt.
aqt to install Qt, you will need to tell
aqt four things:
The host operating system (windows, mac, or linux)
The target SDK (desktop, android, ios, or winrt)
The version of Qt you would like to install
The target architecture
Keep in mind that Qt for IOS is only available on Mac OS, and Qt for WinRT is only available on Windows.
To find out what versions of Qt are available, you can use the aqt list-qt command. This command will print all versions of Qt available for Windows Desktop:
$ aqt list-qt windows desktop 5.9.0 5.9.1 5.9.2 5.9.3 5.9.4 5.9.5 5.9.6 5.9.7 5.9.8 5.9.9 5.10.0 5.10.1 5.11.0 5.11.1 5.11.2 5.11.3 5.12.0 5.12.1 5.12.2 5.12.3 5.12.4 5.12.5 5.12.6 5.12.7 5.12.8 5.12.9 5.12.10 5.12.11 5.13.0 5.13.1 5.13.2 5.14.0 5.14.1 5.14.2 5.15.0 5.15.1 5.15.2 6.0.0 6.0.1 6.0.2 6.0.3 6.0.4 6.1.0 6.1.1 6.1.2 6.2.0
Notice that the version numbers are sorted, grouped by minor version number, and separated by a single space-character. The output of all of the aqt list-qt commands is intended to make it easier for you to write programs that consume the output of aqt list-qt.
Because the aqt list-qt command directly queries the Qt downloads repository at https://download.qt.io/, the results of this command will always be accurate. The Available Qt versions wiki page was last modified at some point in the past, so it may or may not be up to date.
Now that we know what versions of Qt are available, let’s choose version 6.2.0.
The next thing we need to do is find out what architectures are available for
Qt 6.2.0 for Windows Desktop. To do this, we can use aqt list-qt with the
$ aqt list-qt windows desktop --arch 6.2.0 win64_mingw81 win64_msvc2019_64 win64_msvc2019_arm64
Notice that this is a very small subset of the architectures listed in the Available Qt versions wiki page. If we need to use some architecture that is not on this list, we can use the Available Qt versions wiki page to get a rough idea of what versions support the architecture we want, and then use aqt list-qt to confirm that the architecture is available.
Let’s say that we want to install Qt 6.2.0 with architecture win64_mingw81. The installation command we need is:
$ aqt install-qt windows desktop 6.2.0 win64_mingw81
Let’s say that we want to install the next version of Qt 6.2 as soon as it is available. We can do this by using a SimpleSpec instead of an explicit version:
$ aqt install-qt windows desktop 6.2 win64_mingw81
External 7-zip extractor
aqt extracts the 7zip archives stored in the Qt repository using
py7zr, which is installed alongside
aqt. You can specify an alternate 7zip
command path instead by using the
--external flag. For example,
you could use 7-zip on a Windows desktop, using this command:
C:\> aqt install-qt windows desktop 6.2.0 gcc_64 --external 7za.exe
$ aqt install-qt linux desktop 6.2.0 gcc_64 --external 7z
Changing the output directory
aqt will install all of the Qt packages into the current
working directory, in the subdirectory
For example, if we install Qt 6.2.0 for Windows desktop with arch win64_mingw81,
it would end up in
If you would prefer to install it to another location, you
will need to use the
This option also works for all of the other subcommands that begin with
To install to
C:\Qt, the default directory used by the standard gui installer,
you may use this command:
C:\> mkdir Qt C:\> aqt install-qt --outputdir c:\Qt windows desktop 6.2.0 win64_mingw81
Let’s say we need to install some modules for Qt 5.15.2 on Windows Desktop.
First we need to find out what the modules are called, and we can do that
with aqt list-qt with the
Each version of Qt has a different list of modules for each host OS/ target SDK/ architecture
combination, so we will need to supply aqt list-qt with that information:
$ aqt list-qt windows desktop --modules 5.15.2 win64_mingw81 qtcharts qtdatavis3d qtlottie qtnetworkauth qtpurchasing qtquick3d qtquicktimeline qtscript qtvirtualkeyboard qtwebengine qtwebglplugin
Let’s say that we want to install qtcharts and qtnetworkauth. We can do that by using the -m flag with the aqt install-qt command. This flag receives the name of at least one module as an argument:
$ aqt install-qt windows desktop 5.15.2 win64_mingw81 -m qtcharts qtnetworkauth
If we wish to install all the modules that are available, we can do that with the
$ aqt install-qt windows desktop 5.15.2 win64_mingw81 -m all
$ aqt install-qt windows desktop 5.15.2 win64_mingw81 \ -m $(aqt list-qt windows desktop --modules 5.15.2 win64_mingw81)
You will need a Unix-style shell to run this command, or at least git-bash on Windows.
xargs equivalent to this command is an exercise left to the reader.
If you want to install all available modules, you are probably better off using
all keyword, as discussed above. This scripting example is presented to
give you a sense of how to accomplish something more complicated.
Perhaps you want to install all modules except qtnetworkauth; you could write a script
that removes qtnetworkauth from the output of aqt list-qt,
and pipe that into aqt install-qt.
This exercise is left to the reader.
Installing Qt for Android
Let’s install Qt for Android. Installing Qt 5 will be similar to installing Qt for Desktop on Windows, but there will be differences when we get to Qt 6.
$ aqt list-qt windows android # Print Qt versions available 5.9.0 5.9.1 ... ... 6.2.0 $ aqt list-qt windows android --arch 5.15.2 # Print architectures available android $ aqt list-qt windows android --modules 5.15.2 android # Print modules available qtcharts qtdatavis3d qtlottie qtnetworkauth qtpurchasing qtquick3d qtquicktimeline qtscript $ aqt install-qt windows android 5.15.2 android -m qtcharts qtnetworkauth # Install
Let’s see what happens when we try to list architectures and modules for Qt 6:
$ aqt list-qt windows android --arch 6.2.0 # Print architectures available Command line input error: Qt 6 for Android requires one of the following extensions: ('x86_64', 'x86', 'armv7', 'arm64_v8a'). Please add your extension using the `--extension` flag. $ aqt list-qt windows android --modules 6.2.0 android_armv7 # Print modules available Command line input error: Qt 6 for Android requires one of the following extensions: ('x86_64', 'x86', 'armv7', 'arm64_v8a'). Please add your extension using the `--extension` flag.
The Qt 6 for Android repositories are a little different than the Qt 5 repositories, and the aqt list-qt tool doesn’t know where to look for modules and architectures if you don’t tell it what architecture you need. I know, it sounds a little backwards, but that’s how the Qt repo was put together.
There are four architectures available, and the error message from aqt list-qt just told us what they are: x86_64, x86, armv7, and arm64_v8a.
$ aqt list-qt windows android --extension armv7 --arch 6.2.0 android_armv7
You should be thinking, “Well, that was silly. All it did was add android_ to
the beginning of the architecture I gave it. Why do I need to use
aqt list-qt --arch for that?” The answer is,
aqt list-qt --arch is
checking to see what actually exists in the Qt repository. If it prints an error
message, instead of the obvious android_armv7, we would know that Qt 6.2.0
for that architecture doesn’t exist for some reason, and any attempt to install
it with aqt install-qt will fail.
If we want to install Qt 6.2.0 for armv7, we use this command to print available modules:
$ aqt list-qt windows android --extension armv7 --modules 6.2.0 android_armv7 qt3d qt5compat qtcharts qtconnectivity qtdatavis3d qtimageformats qtlottie qtmultimedia qtnetworkauth qtpositioning qtquick3d qtquicktimeline qtremoteobjects qtscxml qtsensors qtserialbus qtserialport qtshadertools qtvirtualkeyboard qtwebchannel qtwebsockets qtwebview
Finally, let’s install Qt 6.2.0 for Android armv7 with the
$ aqt install-qt linux android 6.2.0 android_armv7 -m qtcharts qtnetworkauth
Installing Qt for WASM
To find out how to install Qt for WASM, we need to tell aqt list-qt that we are
using the wasm architecture. We can do that by using the
--extension wasm flag.
$ aqt list-qt windows desktop --extension wasm 5.13.1 5.13.2 5.14.0 5.14.1 5.14.2 5.15.0 5.15.1 5.15.2
There are only a few versions of Qt that support WASM, and they are only available for desktop targets. If we tried this command with android, winrt, or ios targets, we would have seen an error message.
We can check the architecture and modules available as before:
$ aqt list-qt windows desktop --extension wasm --arch 5.15.2 # available architectures wasm_32 $ aqt list-qt windows desktop --extension wasm --modules 5.15.2 wasm_32 # available modules qtcharts qtdatavis3d qtlottie qtnetworkauth qtpurchasing qtquicktimeline qtscript qtvirtualkeyboard qtwebglplugin
We can install Qt for WASM as before:
$ aqt install-qt windows desktop 5.15.2 wasm_32 -m qtcharts qtnetworkauth
Let’s find out what tools are available for Windows Desktop by using the aqt list-tool command:
$ aqt list-tool windows desktop tools_vcredist ... tools_qtcreator tools_qt3dstudio tools_openssl_x86 tools_openssl_x64 tools_openssl_src tools_ninja tools_mingw tools_ifw tools_conan tools_cmake
Let’s see what tool variants are available in tools_mingw:
$ aqt list-tool windows desktop tools_mingw qt.tools.mingw47 qt.tools.win32_mingw48 qt.tools.win32_mingw482 qt.tools.win32_mingw491 qt.tools.win32_mingw492 qt.tools.win32_mingw530 qt.tools.win32_mingw730 qt.tools.win32_mingw810 qt.tools.win64_mingw730 qt.tools.win64_mingw810
This gives us a list of things that we could install using
Let’s see some more details, using the
$ aqt list-tool windows desktop tools_mingw -l Tool Variant Name Version Release Date ============================================================= qt.tools.mingw47 4.7.2-1-1 2013-07-01 qt.tools.win32_mingw48 4.8.0-1-1 2013-07-01 qt.tools.win32_mingw482 4.8.2 2014-05-08 qt.tools.win32_mingw491 4.9.1-3 2016-05-31 qt.tools.win32_mingw492 4.9.2-1 2016-05-31 qt.tools.win32_mingw530 5.3.0-2 2017-04-27 qt.tools.win32_mingw730 7.3.0-1-202004170606 2020-04-17 qt.tools.win32_mingw810 8.1.0-1-202004170606 2020-04-17 qt.tools.win64_mingw730 7.3.0-1-202004170606 2020-04-17 qt.tools.win64_mingw810 8.1.0-1-202004170606 2020-04-17
-l flag causes aqt list-tool to print a table
that shows plenty of data pertinent to each tool variant available in tools_mingw.
aqt list-tool additionally prints the ‘Display Name’
and ‘Description’ for each tool if your terminal is wider than 95 characters;
terminals that are narrower than this cannot display this table in a readable way.
Now let’s install mingw, using the aqt install-tool command. This command receives four parameters:
The host operating system (windows, mac, or linux)
The target SDK (desktop, android, ios, or winrt)
The name of the tool (this is tools_mingw in our case)
(Optional) The tool variant name. We saw a list of these when we ran aqt list-tool with the tool name argument filled in.
To install mingw, you could use this command (please don’t):
$ aqt install-tool windows desktop tools_mingw # please don't run this!
Using this command will install every tool variant available in tools_mingw; in this case, you would install 10 different versions of the same tool. For some tools, like qtcreator or ifw, this is an appropriate thing to do, since each tool variant is a different program. However, for tools like mingw and vcredist, it would make more sense to use aqt list-tool to see what tool variants are available, and then install just the tool variant you are interested in, like this:
$ aqt install-tool windows desktop tools_mingw qt.tools.win64_mingw730
Please note that
aqt install-tool does not recognize the
related to each tool. When you install these tools with the standard gui installer,
the installer may use the
installscript.qs script to make additional changes
to your system. If you need those changes to occur, it will be your responsibility
to make those changes happen, because
aqt is not capable of running this script.
Installing a subset of Qt archives [Advanced]
You may have noticed that by default,
aqt install-qt installs a lot of
archives that you may or may not need, and a typical installation can take up
more disk space than necessary. If you installed the module
may have installed more than 1 gigabyte of data. This section will help you to
reduce the footprint of your Qt installation.
Be careful about using the
--archives flag; it is marked Advanced for a reason!
It is very easy to misuse this command and end up with a Qt installation that
is missing the components that you need.
Don’t use it unless you know what you are doing!
Minimum Qt Installation
Normally, when you run
aqt install-qt, the program will print a long list
of archives that it is downloading, extracting, and installing,
qt3d, and ~25 more items.
We can use the
--archives flag to choose which of these archives we will
In this documentation, “modules”, “archives”, and “the base Qt installation” refer to different things, and are defined here:
Archives: In this context, an archive is a bundle of files compressed with the 7zip algorithm. It exists on a disk drive as a file with the extension
Modules: The Qt repository organizes groups of archives into modules. A module contains one or more archives.
the base Qt installation: By definition, this is just another module that contains 20-30 archives. This documentation refers to it as the base Qt installation instead of a module for several reasons:
aqt install-qtinstalls this module by default.
You cannot specify this module with
aqt install-qt --modules.
aqt list-qt --modulescommand is incapable of printing this module.
aqttransforms the names of modules as they exist in the Qt repository so that they are easier to read and write. If the name of the base Qt installation were transformed using the same rules, the name would be empty.
The fully-qualified name of the base Qt installation module is usually something like
qt.qt6.620.gcc_64. The fully-qualified name of the
qtchartsmodule could be something like
qt.qt6.620.qtcharts.gcc_64. It would be difficult to read and write a list of 20 modules with the prefix
qt.qt6.620.and the suffix
.gcc_64, because these parts are repetitive and not meaningful. Only the
qtchartspart is useful.
Let’s say that we want to install Qt 5.15.2 for Linux desktop, using the gcc_64 architecture.
qtbase archive includes the bare minimum for a working Qt installation,
and we can install it alone with the
$ aqt install-qt linux desktop 5.15.2 --archives qtbase
aqt install-qt will only install one archive,
of the ~27 archives it installs by default.
Installing More Than The Bare Minimum
Let’s say that the
qtbase archive is missing some features that you need.
--archives qtbase flag causes
aqt install-qt to omit roughly 27 archives.
We can print a list of these archives with the
aqt list-qt --archives command:
$ aqt list-qt linux desktop --archives 5.15.2 gcc_64 icu qt3d qtbase qtconnectivity qtdeclarative qtgamepad qtgraphicaleffects qtimageformats qtlocation qtmultimedia qtquickcontrols qtquickcontrols2 qtremoteobjects qtscxml qtsensors qtserialbus qtserialport qtspeech qtsvg qttools qttranslations qtwayland qtwebchannel qtwebsockets qtwebview qtx11extras qtxmlpatterns
Here, we have used the
--archives flag with two arguments:
the version of Qt we are interested in, and the architecture we are using.
As a result, the command printed a list of archives that are part of the base
(non-minimal) Qt installation.
Let’s say we need to use
nothing else. Remember that the
qtbase archive is required for a minimal
working Qt installation. We can install these archives using this command:
$ aqt install-qt linux desktop 5.15.2 --archives qtbase qtmultimedia qtdeclarative qtsvg
Installing Modules With Archives Specified
Now let’s say we need to install the
Let’s see what archives are part of these modules:
$ aqt list-qt linux desktop --archives 5.15.2 gcc_64 qtcharts qtlottie qtcharts qtlottie
This time, the command only printed two archives.
qtlottie modules contain one archive per module.
This command printed all archives associated with the modules we provided it,
and it did not print any of the archives associated with the base Qt installation.
This happened because we added a list of modules to the
# Print archives from the base Qt installation aqt list-qt linux desktop --archives 5.15.2 gcc_64 # Print archives from the specified modules, but not the base Qt installation aqt list-qt linux desktop --archives 5.15.2 gcc_64 qtcharts qtlottie
Now let’s install Qt with these modules:
$ aqt install-qt linux desktop 5.15.2 --modules qtcharts qtlottie \ --archives qtbase qtcharts qtlottie
This command will install the bare minimum Qt, along with the modules
Remember that when using the
--archives flag, you must specify every archive you
intend to install.
# Ways to misuse the `--archives` flag: # This command installs modules without a working Qt installation, # because `--archives` is missing `qtbase`. aqt install-qt linux desktop 5.15.2 --modules qtcharts qtlottie \ --archives qtcharts qtlottie # This command skips installation of the specified modules, # because `--archives` is missing `qtcharts` and `qtlottie`. aqt install-qt linux desktop 5.15.2 --modules qtcharts qtlottie \ --archives qtbase # This command installs qtbase, but neither `qtcharts` nor `qtlottie`, # because `--modules` is missing those names. aqt install-qt linux desktop 5.15.2 --archives qtbase qtcharts qtlottie
If you install modules that depend on archives other than
and you have not specified those archives after the
those modules will not work when you try to use them.
Now let’s say we need to install the
debug_info module, which is particularly large.
We do not want to install all of it, so we can use
aqt list-qt --archives again
to print which archives are part of the
$ aqt list-qt linux desktop --archives 5.15.2 gcc_64 debug_info qt3d qtbase qtcharts qtconnectivity qtdatavis3d qtdeclarative qtgamepad qtgraphicaleffects qtimageformats qtlocation qtlottie qtmultimedia qtnetworkauth qtpurchasing qtquick3d qtquickcontrols qtquickcontrols2 qtquicktimeline qtremoteobjects qtscript qtscxml qtsensors qtserialbus qtserialport qtspeech qtsvg qttools qtvirtualkeyboard qtwayland qtwebchannel qtwebengine qtwebglplugin qtwebsockets qtwebview qtx11extras qtxmlpatterns
This is a lot of archives.
Note that there’s a name collision between the
debug_info archives and the
archives in every other module/Qt base install:
this is because there’s a
debug_info archive that corresponds to almost
every other archive available.
Let’s install Qt with
debug_info with some archives specified:
$ aqt install-qt linux desktop --modules qtcharts debug_info \ --archives qtcharts qtbase qtdeclarative
Notice what we did here: We specified the
and we specified the
This will install a total of 6 archives:
the 3 archives named
the 1 archive
the 2 archives
qtdeclarativefrom the base Qt installation.
aqt install-qt is incapable of installing any archive from
debug_info module without also installing the corresponding module
from the base Qt installation.
For instance, you cannot install the
debug_info archive for
without also installing the usual