From Qt Wiki
Jump to: navigation, search
This guide is for newcomers to Qt on Windows. It explains simple steps to set up Qt and Qt Creator with minimum fuss.
- Note: Qt Creator is separate from Qt. Qt is a multi-purpose library which your applications can use; Qt Creator is an Integrated Development Environment (IDE) which lets you edit, manage, build, and test your projects. It is entirely possible to use Qt without using Qt Creator and vice-versa, but this guide encourages you to use both.
Installation Steps
- Get the installer from the Downloads page.
- Run the installer. Log in with your Qt Account (or create one if you don’t have one).
Note: While optional, a Qt Account lets you participate in the community forums, submit bug reports and feature requests to the issue tracker, contribute code and documentation to the Qt Project, edit articles in the Qt Wiki, and manage your commercial Qt license (if any).
- At the «Installation Folder» page, choose a folder to install Qt. The default (C:\Qt) is recommended unless you don’t have permission to install there.
- At the “Select Components” page, expand and select Qt > Qt [LATEST_VERSION] > MinGW [LATEST_VERSION]. This will install the pre-built Qt libraries which are compatible with the MinGW compiler.
- The example screenshot below shows Qt 5.12.0 for MinGW 7.3.0 being selected (Qt > Qt 5.12.0 > MinGW 7.3.0 64-bit)
- Warning: Be sure to tick the MinGW-specific version of Qt. If you simply tick the Qt version number (like «Qt 5.12.0»), you will install all available builds, which consumes many 10s of gigabytes!
- Ignore any «Preview», «RC» (Release Candidate), or «snapshot» components because these are not fully tested and released yet.
- The example screenshot below shows Qt 5.12.0 for MinGW 7.3.0 being selected (Qt > Qt 5.12.0 > MinGW 7.3.0 64-bit)
- Scroll down to the bottom of the «Select Components» tree. Expand and select Qt > Tools > MinGW [LATEST_VERSION] (the MinGW version must match your selection in step #4). This will install the MinGW compiler itself.
- The example screenshot below shows the MinGW 7.3.0 toolchain being selected (Qt > Tools > MinGW 7.3.0 64-bit):
- Note: This is a special case. Usually, library installers don’t provide compilers! However, the Qt installer provides the MinGW compiler for your convenience.
- The example screenshot below shows the MinGW 7.3.0 toolchain being selected (Qt > Tools > MinGW 7.3.0 64-bit):
- Read and accept the license agreements, keep the default Start Menu shortcuts, and install Qt.
Once installation completes, you are ready to start using Qt.
В этой заметке описывается последовательность действий, необходимых для установки и запуска пакета Qt на Windows 10 с компилятором MSVC2015.
Шаг 1 – скачиваем установщики:
- Qt – с последних версий установщик прячут за тонной просьб купить пакет, если занимаешься коммерческой разработкой. В ближайшем будущем грозятся разрешать скачивание только после регистрации, посмотрим.
- Visual Studio Community
Шаг 2 – устанавливаем Qt:
Maintenance tool: выбор набор библиотек под компилятор MSVC 2015
Можно набрать дополнительных штук:
Maintenance tool: выбор редактора, отладчика и дополнительных штук
Шаг 3 – устанавливаем MSVC 2015, Visual Studio и опционально дополнительные пакеты:
Выбор дополнительных компонентов в Visual Studio Installer
Шаг 3.5 – можно пойти в обход и на главной странице установщика импортировать конфигурацию, чтобы не искать нужные галочки:
Импорт конфигурации установки Visual Studio
Содержимое файла .vsconfig
:
{
"version": "1.0",
"components": [
"Microsoft.VisualStudio.Component.CoreEditor",
"Microsoft.VisualStudio.Workload.CoreEditor",
"Microsoft.VisualStudio.Component.NuGet",
"Microsoft.VisualStudio.Component.Roslyn.Compiler",
"Microsoft.VisualStudio.ComponentGroup.WebToolsExtensions",
"Microsoft.Component.MSBuild",
"Microsoft.VisualStudio.Component.TextTemplating",
"Microsoft.VisualStudio.Component.IntelliCode",
"Microsoft.Component.PythonTools",
"Microsoft.VisualStudio.Component.VC.CoreIde",
"Microsoft.VisualStudio.Component.VC.Tools.x86.x64",
"Microsoft.VisualStudio.Component.Graphics.Tools",
"Microsoft.VisualStudio.Component.VC.DiagnosticTools",
"Microsoft.VisualStudio.Component.Windows10SDK.18362",
"Component.CPython2.x86",
"Microsoft.VisualStudio.Component.Debugger.JustInTime",
"Microsoft.VisualStudio.Component.VC.Redist.14.Latest",
"Microsoft.VisualStudio.ComponentGroup.NativeDesktop.Core",
"Microsoft.VisualStudio.ComponentGroup.WebToolsExtensions.CMake",
"Microsoft.VisualStudio.Component.VC.CMake.Project",
"Microsoft.VisualStudio.Component.VC.ATL",
"Microsoft.VisualStudio.Component.VC.TestAdapterForBoostTest",
"Microsoft.VisualStudio.Component.VC.TestAdapterForGoogleTest",
"Microsoft.VisualStudio.Component.VC.Llvm.Clang",
"Microsoft.Component.VC.Runtime.UCRTSDK",
"Microsoft.VisualStudio.Component.VC.140",
"Microsoft.VisualStudio.Workload.NativeDesktop",
"Component.MDD.Linux",
"Component.Linux.CMake",
"Microsoft.VisualStudio.Workload.NativeCrossPlat"
]
}
Шаг 4 – прописываем в PATH
путь к установленному компилятору:
Установка пути к файлам компилятора в переменную PATH
Нужный путь можно уточнить, зайдя в папку C:\Program Files (x86)\Windows Kits
и выполнить поиск файла rc.exe
, и папку с его расположением добавляем в PATH
:
Поиск
rc.exe
Шаг 5 – настраиваем “набор” для сборки в QtCreator -> Настройки:
QtCreator автоматически настроил комплект сборки
Шаг 6 – готово, можно создавать новый проект!
Время на прочтение
8 мин
Количество просмотров 22K
Пару слов о том для чего это понадобилось вообще: у меня была простая ситуация — не было быстрого интернета и был компьютер с начисто установленной windows 10. К тому же проект, который ковыряю, требует сборки как под 32 так и под 64 битную архитектуру, поэтому мне показалось что наличие Qt, одинаково сконфигуренного и скомпилированного под эти архитектуры будет только плюсом.
0) Желательно заранее отрубить службы Windows Search и Superfetch и защитник винды. Они на наших операциях будут только тормозить систему, а ресурсы нам скоро понадобятся. Кроме того очень полезно сделать языком ввода по умолчанию английский.
1) Создаем папку «C:\QT» — тут будут жить наши сборки.
2) Для начала нам конечно же понадобится сам компилятор mingw-w64. Качаем инсталлер тут.
3) Устанавливаем по очереди обе версии:
первая установка:
Version — 5.2.0 — последняя на момент написания статьи;
Architecture — i686 — сначала ставим 32 битную версию (пускай вас не пугает что оно не i386, i686 это Интел пентиум про и выше, сумеете запустить 2k винду на чем то более древнем — удачи!)
Threads — win32 — если не портируете исходники с юниксов лучше выбрать нативные;
Exeption — sjlj — мне нужно так, если вам нужны другие — бога ради;
Build revision — 1 опять же последняя на момент написания статьи;
Назначение выбрал «C:\mingw-w64-i686» ибо из Program Files могут быть проблемы с пробелами в путях у qt.
Вторая установка все то же самое кроме:
Architecture — x86_64;
Путь «C:\mingw-w64-x86_64»;
Я так же убрал галку «создать ярлыки», иначе они перезапишутся 64 битной версией, мне это неудобно.
Если не хотите плодить много папок в корне ставить можно в «C:\QT\mingw-w64-i686» и «C:\QT\mingw-w64-x86_64» соответвенно архитектурам, роли это не играет.
4) Качаем исходники бибилиотеки QT 4.8.7 тут
5) Распаковываем сам Qt (тут лучше заранее озаботится наличием программы 7zip ибо виндовый архиватор сначала будет распаковывать во временную папку, потом копировать из нее туеву хучу мелких файлов, идиот, а потом ещё и создаст дополнительную папку внутри с тем же именем) сразу в 2 копии «C:\QT\qt-4.8.7-mingw-w64-i686» и «C:\QT\qt-4.8.7-mingw-w64-x64» (вторая нужна на случай ошибок при конфигуре, гораздо быстрее переименовать копию и пустить фоном распаковываться ещё одну, чем ждать пока отработает mingw32-make confclean). Если не уверены в архиваторе проверяем чтобы в этих папках сразу были папки bin, util, src и т.д., если архиватор создал ещё одну вложенную — вытаскиваем содержимое на уровень выше.
6) Идем в свойства системы и меняем переменную PATH (надо же в моей 10-ке сделали нормальный интерфейс для этого) добавляем туда путь пока только к 32 битной версии компилятора, у меня это: «C:\mingw-w64-i686\mingw32\bin». Если вдруг у вас в PATH есть пути к другим компиляторам временно убираем их оттуда.
7) Запускаем cmd от админа (это важно) и вводим:
g++ -v
должна появится инфа о компиляторе, если этого не произошло значит компиль установлен неправильно, ищем ошибку на предыдущих шагах. Если вывелась информация проверяем, что мы ничего не напутали: у нас запускается действительно 32 битная версия, и что она именно та которую мы установили на предыдущих шагах, а не из оригинального mingw без w64 (это по сути разные проекты) или, прости господи, вижуал студии.
Если все нормально переходим в папку с Qt:
cd C:\QT\qt-4.8.7-mingw-w64-i586
запускаем там конфигур как-то так:
.\configure -debug-and-release -opensource -confirm-license -platform win32-g++ -graphicssystem raster -no-openssl -nis -iconv -system-proxies -no-freetype -plugin-sql-odbc -plugin-sql-sqlite -qt-style-windows -qt-style-windowsxp -qt-style-windowsvista -qt-style-plastique -qt-style-cleanlooks -qt-style-motif -qt-style-cde -qt-style-windowsce -qt-style-windowsmobile -qt-style-s60
в этом конфиге по максимому все что можно собрать без зависимостей. Мне openssl не очень нужен, иначе его нужно собрать заранее. Если критично время можно отключить примеры, не собирать дополнительные темы и odbc плагин. Справку по опциям можно получить так: «.\configure -help». Далее ждем несколько минут пока отработает конфигур, и запускаем компиляцию:
mingw32-make -j4
у меня 4 ядерный процессор по этому опция -j4 она обозначает делать компиляцию в 4 потока. Сразу оговорюсь, компиляция с этой опцией до конца не проходит, грохается на qtdeclarative с ошибкой копирования файла, видимо где то неправильно прописаны зависимости. Мне достаточно было запустить компиляцию после сбоя ещё раз. Ошибка кстати повторилась и на 64 битной версии. На core i5-3570 c 8-ю гигами оперы компиляция одной версии в 4 потока занимает почти 2 часа.
Если у вас медленный интернет, пока компилится сам Qt можно поставить на закачку qt creator 3.2.2 (это последняя версия, которая компилится на 4.8.x), ActivePerl-5.20.2 !32 битную версию! и msysgit !32 битную версию! Указанные тут верcии это последние на момент написания статьи, и, соответственно, те с которыми работал я. Если у вас что-то не пошло на более новых, попробуйте указанные мной. Предупрежу сразу, до сборки qtcreator ставить msysgit очень не желательно, креатор нормально не соберется если увидит в патче sh.exe, а для нормальной работы с гитом его как раз стоит ставить с прописыванием PATH.
9) Устанавливаем perl: я не ставил документацию и примеры, местом назначения сделал «C:\perlx86». Галку «Add perl to the PATH environment variable» не снимаем. После установки в командной строке (естественно не в той, в которой компилится Qt) пишем «perl -v», должна появится информация о версии.
10) Распаковываем qt creator в » C:\QT\qt-creator-opensource-src-3.2.2″, так же проверяем чтобы внутри не было вложенной папки, а сразу были папка bin и остальное.
11) Ждем когда компилируется qt. Никаких прямых сообщений что компиляция завершена успешно, не будет. У меня последним собрался ‘C:/QT/qt-4.8.7-mingw-w64-i586/demos/declarative/webbrowser’. Можно запустить qtdemo.exe для проверки, позапускать примеры. Снова открываем редактор переменных среды, дописываем в PATH «C:\QT\qt-4.8.7-mingw-w64-i586\bin». Опять же убеждаемся, что это единственный профиль qt в PATH. Проверяем себя, перезапустив командную строку и набрав «qmake -v».
12) Открываем блокном файл «C:\QT\qt-creator-opensource-src-3.2.2\src\libs\utils\tcpportsgatherer.cpp», находим строчку
#if __GNUC__ == 4 && (!defined(__MINGW64_VERSION_MAJOR) || __MINGW64_VERSION_MAJOR < 2)
и меняем её на
#if __MINGW64_VERSION_MAJOR == 5 || (__GNUC__ == 4 && (!defined(__MINGW64_VERSION_MAJOR) || __MINGW64_VERSION_MAJOR < 2))
13) Перезапускаем cmd опять же от админа. Собираем creator в новой папке:
mkdir C:\QT\qt-creator-3.2.2-x86
cd C:\QT\qt-creator-3.2.2-x86
qmake -r ../qt-creator-opensource-src-3.2.2/qtcreator.pro
mingw32-make release -j4
надеюсь, повторяться про опцию -j4 не надо.
14) Ждем окончания компиляции, запускаем qtcreator, убеждаемся что работает. Закрываем, настраивать в нем пока ещё нечего. Если очень жалко места на диске и оперативы, можно уже скомпиленный creator закинуть в папку с Qt (скопировать только папки bin, lib, share) и добросить в папку bin недостающие dll-ки из mingw. По человечески же, надо наоборот: убрать компилятор и Qt из PATH и докопировать в папку bin creator-а dll-ки из папок bin от Qt и компилятора.
15) Снова открываем редактор PATH убираем оттуда путь к скомпиленному Qt «C:\QT\qt-4.8.7-mingw-w64-i586\bin» и меняем путь к компилятору c «C:\mingw-w64-i686\mingw32\bin» на «C:\mingw-w64-x86_64\mingw64\bin». Опять же перезапускаем cmd от админа и проверяем что нам выдаст
g++ -v
если все в норме, делаем все то же самое что и в шаге 6, только путь у нас теперь будет другой.
cd C:\QT\qt-4.8.7-mingw-w64-x86_64
.\configure -debug-and-release -opensource -confirm-license -platform win32-g++ -graphicssystem raster -no-openssl -nis -iconv -system-proxies -no-freetype -plugin-sql-odbc -plugin-sql-sqlite -qt-style-windows -qt-style-windowsxp -qt-style-windowsvista -qt-style-plastique -qt-style-cleanlooks -qt-style-motif -qt-style-cde -qt-style-windowsce -qt-style-windowsmobile -qt-style-s60
mingw32-make -j4
16) Теперь, пока компилится 64 битная версия Qt, можно заняться и гитом (джитом, не знаю какая транскрипция правильнее). Устанавливаем msysgit v2.6.3 !32 битную версию! запускаем инсталлер сразу от админа, иначе он поставит нам версию только для локального пользователя, оно нам не надо. Путь я выбрал «C:\msysGitX86». На следующем шаге можно ткнуть галку, которая создаст ярлык к консоли на рабочем столе. Eщё через шаг выбираем «Use git from the Windows Command Promt», Я еще выбрал «Use Windows` default console window» для терминала, остальное на любителя или по умолчанию.
На blogspot есть замечательная статья о том как подружить qt creator и github. Однако в ней не даны инструкции что делать если винт на котором все это настроено сгорел синим пламенем. Попробуем восполнить этот пробел.
17) Запускаем git-bash от админа, с ярлыка который нам создал установщик
делаем настройки, конечно же подставив ту почту на которую зарегистрирован аккаунт на гитхабе и свой никнейм
git config --global user.email "myMail@example.com"
git config --global user.name "myGithubNick"
git config --global push.default simple
генерим новую пару ключей для ssh:
ssh-keygen -t rsa -C "myMail@example.com"
3 раза жмакаем enter, заходим браузером в свой профиль на гитхабе, удаляем старый ключ (если конечно не собираемся им пользоваться, а он утрачен как у меня) и добавляем новый.
пробуем склонировать существующий репозиторий:
mkdir C:\\myproject
cd C:\\myproject
git clone git@github.com:myGithubNick/mysuperproject.git
обратите внимание что пользователь «git», а не никнейм; никнейм указывается уже после двоеточия. Кроме того никаких https:// или git:// перед адресом быть не должно, если получаете сообщение, что нужно использовать https, значит гитхаб не опознал в вас владельца репозитория, ищите проблемы с ключами или ssh. Если все в порядке, гит сделает нам копию репозитория в папке mysuperproject. Зайдем в нее и проверим что репозиторий рабочий, и у нас есть все права
cd ./mysuperproject
git remote -v
touch .testfile.txt
git add .testfile.txt
git commit -m test
git push
git reset --hard HEAD~1
git push -f
естественно ошибок быть не должно, если есть значит что-то не так с установкой гита или ssh.
18) Дожидаемся пока скомпилится 64 битная версия Qt. Убираем из PATH 64 битный компилятор, либо совсем, либо меняем на 32 битную версию, это уже как удобнее. Открываем блокнотом «C:\QT\qt-4.8.7-mingw-w64-x86_64\mkspecs\win32-g++\qmake.conf», сразу после комментов дописываем «QMAKE_TARGET.arch += x86_64», сохраняем, закрываем.
19) Снова запускаем creator (если сейчас он перестал запускаться, значит что-то лишнее есть в path или не все библиотеки мы ему подложили).
Открываем Инструменты(Tools)->Параметры(Options). Сразу же в разделе Среда(Environment) на вкладке Основные(General) нас просят ввести путь к командe patch, можно использовать «C:\msysGitX86\usr\bin\patch.exe». Идём во Внешние утилиты(External Tools) — правим пути.
Переходим в раздел Сборка и запуск(Build & Run), переходим на вкладку Отладчики(Debuggers), нажмаем Добавить(Add), название даем: «mingw32-w64-gdb», путь: «C:\mingw-w64-i686\mingw32\bin\gdb.exe». Снова жмем Добавить(Add), название даем: «mingw64-w64-gdb», путь: «C:\mingw-w64-x86_64\mingw64\bin\gdb.exe».
Переходим на вкладку Компиляторы(Compilers), нажмаем Добавить(Add) ->MinGW, если нет определенных в path имя даем «MinGW32-W64» и путь «C:\mingw-w64-i686\mingw32\bin\g++.exe» (можно и копию сделать для удобства, не страшно). Добавляем ещё один: имя «MinGW64-W64» путь «C:\mingw-w64-x86_64\mingw64\bin\g++.exe», ABI выбираем 64битные, если есть.
Переходим на вкладку Профили Qt (Qt versions), Если 32 битного профиля нет в path добавляем сначала его «C:\QT\qt-4.8.7-mingw-w64-i586\bin\qmake.exe». Потом добавляем 64 битный «C:\QT\qt-4.8.7-mingw-w64-x86_64\bin\qmake.exe». Имена у меня «Qt 4.8.7 mingw-w64 i586» и «Qt 4.8.7 mingw-w64 x86_64» соответвенно.
Переходим на вкладку Комплекты(kits), сначала настраиваем профиль Desktop:
Название:Desktop
Имя в файловой системе: x86
Тип устройства:Desktop
Устройство: Локальный ПК
Sysroot: — оставляем пустым
Компилятор: MinGW32-W64
Отладчик: mingw32-w64-gdb
Профиль Qt: Qt 4.8.7 mingw-w64 i586
Добавляем ещё один
Название:Desktop 64
Имя в файловой системе: x86_64
Тип устройства:Desktop
Устройство: Локальный ПК
Sysroot: — оставляем пустым
Компилятор: MinGW64-W64
Отладчик: mingw64-w64-gdb
Профиль Qt: Qt 4.8.7 mingw-w64 ч86_64
сохраняем, применяем, пробуем что-нибудь собрать.
Вот пожалуй и все что вспомнил по данной теме.
Кстати небольшой хак: если нужно незначительно переконфигурить уже собранную сборку, ну например openssl вы решили добавить или плагин к какому-нить мускулю не собрался, а 2-3-4 часа ждать пока все перекомпилиться ни разу не улыбается, делаем так: выставляем системное время на минут 10-15 раньше чем последний раз конфигурили сборку, переконфигуриваем, возвращаем время на настоящее. Блокнотом изменяем тот(те) мейкфайл(ы) который(е) затрагивает(ют) наши изменения и запускаем мейк, если не ошиблись с мейкфайлами (на самом деле если знать из чего состоит Qt, и что от чего зависит, ошибится трудно) перекомпилится только тот кусок который нам нужен.
Qt Creator
Qt Creator is a cross-platform, integrated development environment (IDE) for
application developers to create applications for multiple desktop, embedded,
and mobile device platforms.
The Qt Creator Manual is available at:
https://doc.qt.io/qtcreator/index.html
For an overview of the Qt Creator IDE, see:
https://doc.qt.io/qtcreator/creator-overview.html
Supported Platforms
The standalone binary packages support the following platforms:
- Windows 10 (64-bit) or later
- (K)Ubuntu Linux 20.04 (64-bit) or later
- macOS 10.15 or later
Contributing
For instructions on how to set up the Qt Creator repository to contribute
patches back to Qt Creator, please check:
https://wiki.qt.io/Setting_up_Gerrit
See the following page for information about our coding standard:
https://doc.qt.io/qtcreator-extending/coding-style.html
Compiling Qt Creator
Prerequisites:
- Qt 6.2 or later. The Qt version that you use to build Qt Creator defines the
minimum platform versions that the result supports
(Windows 10, RHEL/CentOS 8.4, Ubuntu 20.04, macOS 10.15 for Qt 6.2). - Qt WebEngine module for QtWebEngine based help viewer
- On Windows:
- MinGW with GCC 9 or Visual Studio 2019 or later
- Python 3.5 or later (optional, needed for the python enabled debug helper)
- Debugging Tools for Windows (optional, for MSVC debugging support with CDB)
- On Mac OS X: latest Xcode
- On Linux: GCC 9 or later
- LLVM/Clang 10 or later (optional, LLVM/Clang 14 is recommended.
See instructions on how to
get LLVM.
The ClangFormat plugin uses the LLVM C++ API.
Since the LLVM C++ API provides no compatibility guarantee,
if later versions don’t compile we don’t support that version.) - CMake
- Ninja (recommended)
The used toolchain has to be compatible with the one Qt was compiled with.
Getting Qt Creator from Git
The official mirror of the Qt Creator repository is located at
https://code.qt.io/cgit/qt-creator/qt-creator.git/. Run
git clone https://code.qt.io/qt-creator/qt-creator.git
to clone the Qt Creator sources from there. This creates a checkout of the
Qt Creator sources in the qt-creator/
directory of your current working
directory.
Qt Creator relies on some submodules, like
litehtml for displaying documentation. Get these
submodules with
cd qt-creator # switch to the sources, if you just ran git clone
git submodule update --init --recursive
Note the --recursive
in this command, which fetches also submodules within
submodules, and is necessary to get all the sources.
The git history contains some coding style cleanup commits, which you might
want to exclude for example when running git blame
. Do this by running
git config blame.ignoreRevsFile .gitignore-blame
Linux and macOS
These instructions assume that Ninja is installed and in the PATH
, Qt Creator
sources are located at /path/to/qtcreator_sources
, Qt is installed in
/path/to/Qt
, and LLVM is installed in /path/to/llvm
.
Note that if you install Qt via the online installer, the path to Qt must
include the version number and compiler ABI. The path to the online installer
content is not enough.
Note that /path/to/Qt
doesn’t imply the full path depth like:
$USER/Qt/6.2.4/gcc_64/lib/cmake/Qt6
, but only $USER/Qt/6.2.4/gcc_64
.
See instructions on how to
get LLVM.
mkdir qtcreator_build
cd qtcreator_build
cmake -DCMAKE_BUILD_TYPE=Debug -G Ninja "-DCMAKE_PREFIX_PATH=/path/to/Qt;/path/to/llvm" /path/to/qtcreator_sources
cmake --build .
Windows
These instructions assume that Ninja is installed and in the PATH
, Qt Creator
sources are located at \path\to\qtcreator_sources
, Qt is installed in
\path\to\Qt
, and LLVM is installed in \path\to\llvm
.
Note that if you install Qt via the online installer, the path to Qt must
include the version number and compiler ABI. The path to the online installer
content is not enough.
Note that \path\to\Qt
doesn’t imply the full path depth like:
c:\Qt\6.2.4\msvc2019_64\lib\cmake\Qt6
, but only c:/Qt/6.2.4/msvc2019_64
.
The usage of slashes /
is intentional, since CMake has issues with backslashes \
in CMAKE_PREFX_PATH
, they are interpreted as escape codes.
See instructions on how to
get LLVM.
Decide which compiler to use: MinGW or Microsoft Visual Studio.
MinGW is available via the Qt online installer, for other options see
https://wiki.qt.io/MinGW. Run the commands below in a shell prompt that has
<path_to_mingw>\bin
in the PATH
.
For Microsoft Visual C++ you can use the «Build Tools for Visual Studio». Also
install the «Debugging Tools for Windows» from the Windows SDK installer. We
strongly recommend using the 64-bit version and 64-bit compilers on 64-bit
systems. Open the x64 Native Tools Command Prompt for VS <version>
from the
start menu items that were created for Visual Studio, and run the commands
below in it.
md qtcreator_build
cd qtcreator_build
cmake -DCMAKE_BUILD_TYPE=Debug -G Ninja "-DCMAKE_PREFIX_PATH=/path/to/Qt;/path/to/llvm" \path\to\qtcreator_sources
cmake --build .
Qt Creator can be registered as a post-mortem debugger. This can be done in the
options page or by running the tool qtcdebugger with administrative privileges
passing the command line options -register/unregister, respectively.
Alternatively, the required registry entries
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\AeDebug
can be modified using the registry editor regedt32 to contain
qtcreator_build\bin\qtcdebugger %ld %ld
When using a self-built version of Qt Creator as post-mortem debugger, it needs
to be able to find all dependent Qt-libraries and plugins when being launched
by the system. The easiest way to do this is to create a self-contained Qt
Creator by installing it and installing its dependencies. See «Options» below
for details.
Note that unlike on Unix, you cannot overwrite executables that are running.
Thus, if you want to work on Qt Creator using Qt Creator, you need a separate
installation of it. We recommend using a separate, release-built version of Qt
Creator to work on a debug-built version of Qt Creator.
Alternatively, take the following template of CMakeUserPresets.json
for
reference. Write your own configurePreset inheriting cmake-plugin-minimal
in
CMakeUserPresets.json
to build with IDEs (such as QtCreator, VSCode,
CLion…etc) locally:
{ "version": 4, "cmakeMinimumRequired": { "major": 3, "minor": 23, "patch": 0 }, "configurePresets": [ { "name": "custom", "displayName": "custom", "description": "custom", "inherits": "cmake-plugin-minimal", "binaryDir": "${sourceDir}/build/${presetName}", "toolset": { "value": "v142,host=x64", "strategy": "external" }, "architecture": { "value": "x64", "strategy": "external" }, "cacheVariables": { "CMAKE_CXX_COMPILER": "cl.exe", "CMAKE_C_COMPILER": "cl.exe", "CMAKE_PREFIX_PATH": "c:/Qt/6.2.4/msvc2019_64" } } ] }
Options
If you do not have Ninja installed and in the PATH
, remove -G Ninja
from
the first cmake
call. If you want to build in release mode, change the build
type to -DCMAKE_BUILD_TYPE=Release
. You can also build with release
optimizations but debug information with -DCMAKE_BUILD_TYPE=RelWithDebInfo
.
You can find more options in the generated CMakeCache.txt file. For instance,
building of Qbs together with Qt Creator can be enabled with -DBUILD_QBS=ON
.
Installation is not needed. You can run Qt Creator directly from the build
directory. On Windows, make sure that your PATH
environment variable points to
all required DLLs, like Qt and LLVM. On Linux and macOS, the build already
contains the necessary RPATH
s for the dependencies.
If you want to install Qt Creator anyway, that is however possible using
cmake --install . --prefix /path/to/qtcreator_install
To create a self-contained Qt Creator installation, including all dependencies
like Qt and LLVM, additionally run
cmake --install . --prefix /path/to/qtcreator_install --component Dependencies
To install development files like headers, CMake files, and .lib
files on
Windows, run
cmake --install . --prefix /path/to/qtcreator_install --component Devel
If you used the RelWithDebInfo
configuration and want debug information to be
available to the installed Qt Creator, run
cmake --install . --prefix /path/to/qtcreator_install --component DebugInfo
Perf Profiler Support
Support for the perf profiler
requires the perfparser
tool that is part of the Qt Creator source package, and also
part of the Qt Creator Git repository in form of a submodule in src/tools/perfparser
.
Compilation of perfparser
requires ELF and DWARF development packages.
You can either download and extract a prebuilt package from
https://download.qt.io/development_releases/prebuilt/elfutils/ and add the
directory to the CMAKE_PREFIX_PATH
when configuring Qt Creator,
or install the libdw-dev
package on Debian-style Linux systems.
You can also point Qt Creator to a separate installation of perfparser
by
setting the PERFPROFILER_PARSER_FILEPATH
environment variable to the full
path to the executable.
Getting LLVM/Clang for the Clang Code Model
The Clang code model uses Clangd
and the ClangFormat plugin depends on the
LLVM/Clang libraries. The currently recommended LLVM/Clang version is 14.0.
Prebuilt LLVM/Clang packages
Prebuilt packages of LLVM/Clang can be downloaded from
https://download.qt.io/development_releases/prebuilt/libclang/
This should be your preferred option because you will use the version that is
shipped together with Qt Creator (with backported/additional patches). In
addition, MinGW packages for Windows are faster due to profile-guided
optimization. If the prebuilt packages do not match your configuration, you
need to build LLVM/Clang manually.
If you use the MSVC compiler to build Qt Creator the suggested way is:
1. Download both MSVC and MinGW packages of libclang.
2. Use the MSVC version of libclang during the Qt Creator build.
3. Prepend PATH variable used for the run time with the location of MinGW version of libclang.dll.
4. Launch Qt Creator.
Building LLVM/Clang manually
You need to install CMake in order to build LLVM/Clang.
Build LLVM/Clang by roughly following the instructions at
http://llvm.org/docs/GettingStarted.html#git-mirror:
-
Clone LLVM/Clang and checkout a suitable branch
git clone -b release_130-based --recursive https://code.qt.io/clang/llvm-project.git
-
Build and install LLVM/Clang
For Linux/macOS:
cmake \ -D CMAKE_BUILD_TYPE=Release \ -D LLVM_ENABLE_RTTI=ON \ -D LLVM_ENABLE_PROJECTS="clang;clang-tools-extra" \ -D CMAKE_INSTALL_PREFIX=<installation location> \ ../llvm-project/llvm cmake --build . --target install
For Windows:
cmake ^ -G Ninja ^ -D CMAKE_BUILD_TYPE=Release ^ -D LLVM_ENABLE_RTTI=ON ^ -D LLVM_ENABLE_PROJECTS="clang;clang-tools-extra" ^ -D CMAKE_INSTALL_PREFIX=<installation location> ^ ..\llvm-project\llvm cmake --build . --target install
Clang-Format
The ClangFormat plugin depends on the additional patch
https://code.qt.io/cgit/clang/llvm-project.git/commit/?h=release_130-based&id=42879d1f355fde391ef46b96a659afeb4ad7814a
While the plugin builds without it, it might not be fully functional.
Note that the plugin is disabled by default.
Licenses and Attributions
Qt Creator is available under commercial licenses from The Qt Company,
and under the GNU General Public License version 3,
annotated with The Qt Company GPL Exception 1.0.
See LICENSE.GPL-EXCEPT for the details.
Qt Creator furthermore includes the following third-party components,
we thank the authors who made this possible:
YAML Parser yaml-cpp (MIT License)
https://github.com/jbeder/yaml-cpp
QtCreator/src/libs/3rdparty/yaml-cpp
Copyright (c) 2008-2015 Jesse Beder.
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the «Software»), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED «AS IS», WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
KSyntaxHighlighting
Syntax highlighting engine for Kate syntax definitions
This is a stand-alone implementation of the Kate syntax highlighting
engine. It’s meant as a building block for text editors as well as
for simple highlighted text rendering (e.g. as HTML), supporting both
integration with a custom editor as well as a ready-to-use
QSyntaxHighlighter sub-class.
Distributed under the:
MIT License
Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
«Software»), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:
The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED «AS IS», WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
The source code of KSyntaxHighlighting can be found here:
https://cgit.kde.org/syntax-highlighting.git
QtCreator/src/libs/3rdparty/syntax-highlighting
https://code.qt.io/cgit/qt-creator/qt-creator.git/tree/src/libs/3rdparty/syntax-highlighting
Clazy
https://github.com/KDE/clazy
Copyright (C) 2015-2018 Clazy Team
Distributed under GNU LIBRARY GENERAL PUBLIC LICENSE Version 2 (LGPL2).
Integrated with patches from
https://code.qt.io/cgit/clang/clazy.git/.
LLVM/Clang
https://github.com/llvm/llvm-project.git
Copyright (C) 2003-2019 LLVM Team
Distributed under the Apache 2.0 License with LLVM exceptions,
see https://github.com/llvm/llvm-project/blob/main/clang/LICENSE.TXT
With backported/additional patches from https://code.qt.io/cgit/clang/llvm-project.git
std::span implementation for C++11 and later
A single-header implementation of C++20’s std::span, conforming to the C++20
committee draft. It is compatible with C++11, but will use newer language
features if they are available.
https://github.com/martinmoene/span-lite
QtCreator/src/libs/3rdparty/span
Copyright 2018-2021 Martin Moene
Distributed under the Boost Software License, Version 1.0.
(See accompanying file LICENSE.md or copy at http://boost.org/LICENSE_1_0.txt)
Open Source front-end for C++ (license MIT), enhanced for use in Qt Creator
Roberto Raggi roberto.raggi@gmail.com
QtCreator/src/libs/3rdparty/cplusplus
Copyright 2005 Roberto Raggi roberto@kdevelop.org
Permission to use, copy, modify, distribute, and sell this software and its
documentation for any purpose is hereby granted without fee, provided that
the above copyright notice appear in all copies and that both that
copyright notice and this permission notice appear in supporting
documentation.
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED «AS IS», WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
KDEVELOP TEAM BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN
AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Open Source tool for generating C++ code that classifies keywords (license MIT)
Roberto Raggi roberto.raggi@gmail.com
QtCreator/src/tools/3rdparty/cplusplus-keywordgen
Copyright (c) 2007 Roberto Raggi roberto.raggi@gmail.com
Permission is hereby granted, free of charge, to any person obtaining a copy of
this software and associated documentation files (the «Software»), to deal in
the Software without restriction, including without limitation the rights to
use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
the Software, and to permit persons to whom the Software is furnished to do so,
subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED «AS IS», WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
SQLite (version 3.8.10.2)
SQLite is a C-language library that implements a small, fast, self-contained,
high-reliability, full-featured, SQL database engine.
SQLite (https://www.sqlite.org) is in the Public Domain.
ClassView and ImageViewer plugins
Copyright (C) 2016 The Qt Company Ltd.
All rights reserved.
Copyright (C) 2016 Denis Mingulov.
Contact: http://www.qt.io
This file is part of Qt Creator.
You may use this file under the terms of the BSD license as follows:
«Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
* Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
* Neither the name of The Qt Company Ltd and its Subsidiary(-ies) nor
the names of its contributors may be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
«AS IS» AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.»
Source Code Pro font
Copyright 2010, 2012 Adobe Systems Incorporated (http://www.adobe.com/),
with Reserved Font Name ‘Source’. All Rights Reserved. Source is a
trademark of Adobe Systems Incorporated in the United States
and/or other countries.
This Font Software is licensed under the SIL Open Font License, Version 1.1.
The font and license files can be found in QtCreator/src/libs/3rdparty/fonts.
JSON Library by Niels Lohmann
Used by the Chrome Trace Format Visualizer plugin instead of QJson
because of QJson’s current hard limit of 128 Mb object size and
trace files often being much larger.
The sources can be found in QtCreator/src/libs/3rdparty/json
.
The class is licensed under the MIT License:
Copyright © 2013-2019 Niels Lohmann
Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files (the “Software”), to
deal in the Software without restriction, including without limitation the
rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is furnished
to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
The class contains the UTF-8 Decoder from Bjoern Hoehrmann which is
licensed under the MIT License (see above). Copyright © 2008-2009 Björn
Hoehrmann bjoern@hoehrmann.de
The class contains a slightly modified version of the Grisu2 algorithm
from Florian Loitsch which is licensed under the MIT License (see above).
Copyright © 2009 Florian Loitsch
litehtml
The litehtml HTML/CSS rendering engine is used as a help viewer backend
to display help files.
The sources can be found in:
* QtCreator/src/plugins/help/qlitehtml
* https://github.com/litehtml
Copyright (c) 2013, Yuri Kobets (tordex)
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
- Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer. - Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution. - Neither the name of the nor the
names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS «AS IS» AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
gumbo
The litehtml HTML/CSS rendering engine uses the gumbo parser.
Copyright 2010, 2011 Google
Licensed under the Apache License, Version 2.0 (the «License»);
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an «AS IS» BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
gumbo/utf8.c
The litehtml HTML/CSS rendering engine uses gumbo/utf8.c parser.
Copyright (c) 2008-2009 Bjoern Hoehrmann bjoern@hoehrmann.de
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the «Software»), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
SourceCodePro fonts
Qt Creator ships with the following fonts licensed under OFL-1.1:
- SourceCodePro-Regular.ttf
- SourceCodePro-It.ttf
- SourceCodePro-Bold.ttf
SIL OPEN FONT LICENSE
Version 1.1 — 26 February 2007
PREAMBLE
The goals of the Open Font License (OFL) are to stimulate worldwide
development of collaborative font projects, to support the font creation
efforts of academic and linguistic communities, and to provide a free and
open framework in which fonts may be shared and improved in partnership
with others.
The OFL allows the licensed fonts to be used, studied, modified and
redistributed freely as long as they are not sold by themselves. The
fonts, including any derivative works, can be bundled, embedded,
redistributed and/or sold with any software provided that any reserved
names are not used by derivative works. The fonts and derivatives,
however, cannot be released under any other type of license. The
requirement for fonts to remain under this license does not apply
to any document created using the fonts or their derivatives.
DEFINITIONS
«Font Software» refers to the set of files released by the Copyright
Holder(s) under this license and clearly marked as such. This may
include source files, build scripts and documentation.
«Reserved Font Name» refers to any names specified as such after the
copyright statement(s).
«Original Version» refers to the collection of Font Software components as
distributed by the Copyright Holder(s).
«Modified Version» refers to any derivative made by adding to, deleting,
or substituting — in part or in whole — any of the components of the
Original Version, by changing formats or by porting the Font Software to a
new environment.
«Author» refers to any designer, engineer, programmer, technical
writer or other person who contributed to the Font Software.
PERMISSION & CONDITIONS
Permission is hereby granted, free of charge, to any person obtaining
a copy of the Font Software, to use, study, copy, merge, embed, modify,
redistribute, and sell modified and unmodified copies of the Font
Software, subject to the following conditions:
-
Neither the Font Software nor any of its individual components,
in Original or Modified Versions, may be sold by itself. -
Original or Modified Versions of the Font Software may be bundled,
redistributed and/or sold with any software, provided that each copy
contains the above copyright notice and this license. These can be
included either as stand-alone text files, human-readable headers or
in the appropriate machine-readable metadata fields within text or
binary files as long as those fields can be easily viewed by the user. -
No Modified Version of the Font Software may use the Reserved Font
Name(s) unless explicit written permission is granted by the corresponding
Copyright Holder. This restriction only applies to the primary font name as
presented to the users. -
The name(s) of the Copyright Holder(s) or the Author(s) of the Font
Software shall not be used to promote, endorse or advertise any
Modified Version, except to acknowledge the contribution(s) of the
Copyright Holder(s) and the Author(s) or with their explicit written
permission. -
The Font Software, modified or unmodified, in part or in whole,
must be distributed entirely under this license, and must not be
distributed under any other license. The requirement for fonts to
remain under this license does not apply to any document created
using the Font Software.
TERMINATION
This license becomes null and void if any of the above conditions are
not met.
DISCLAIMER
THE FONT SOFTWARE IS PROVIDED «AS IS», WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
OTHER DEALINGS IN THE FONT SOFTWARE.
Qbs
Qt Creator installations deliver Qbs. Its licensing and third party
attributions are listed in Qbs Manual at
https://doc.qt.io/qbs/attributions.html
conan.cmake
CMake script used by Qt Creator’s auto setup of package manager dependencies.
The sources can be found in:
* QtCreator/src/share/3rdparty/package-manager/conan.cmake
* https://github.com/conan-io/cmake-conan
The MIT License (MIT)
Copyright (c) 2018 JFrog
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the «Software»), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED «AS IS», WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
TartanLlama/expected
Implementation of std::expected compatible with C++11/C++14/C++17.
https://github.com/TartanLlama/expected
To the extent possible under law, the author(s) have dedicated all
copyright and related and neighboring rights to this software to the
public domain worldwide. This software is distributed without any warranty.
http://creativecommons.org/publicdomain/zero/1.0/
WinPty
Implementation of a pseudo terminal for Windows.
https://github.com/rprichard/winpty
The MIT License (MIT)
Copyright (c) 2011-2016 Ryan Prichard
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the «Software»), to
deal in the Software without restriction, including without limitation the
rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
sell copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED «AS IS», WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
IN THE SOFTWARE.
ptyqt
Pty-Qt is small library for access to console applications by pseudo-terminal interface on Mac,
Linux and Windows. On Mac and Linux it uses standard PseudoTerminal API and on Windows it uses
WinPty(prefer) or ConPty.
https://github.com/kafeg/ptyqt
MIT License
Copyright (c) 2019 Vitaly Petrov, v31337@gmail.com
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the «Software»), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED «AS IS», WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
libvterm
An abstract C99 library which implements a VT220 or xterm-like terminal emulator.
It doesn’t use any particular graphics toolkit or output system, instead it invokes callback
function pointers that its embedding program should provide it to draw on its behalf.
It avoids calling malloc() during normal running state, allowing it to be used in embedded kernel
situations.
https://www.leonerd.org.uk/code/libvterm/
The MIT License
Copyright (c) 2008 Paul Evans leonerd@leonerd.org.uk
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the «Software»), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED «AS IS», WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
terminal/shellintegrations
The Terminal plugin uses scripts to integrate with the shell. The scripts are
located in the Qt Creator source tree in src/plugins/terminal/shellintegrations.
https://github.com/microsoft/vscode/tree/main/src/vs/workbench/contrib/terminal/browser/media
MIT License
Copyright (c) 2015 — present Microsoft Corporation
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the «Software»), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED «AS IS», WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
terminal/shellintegrations/clink
The Terminal plugin uses a lua script to integrate with the cmd shell when using clink.
https://github.com/chrisant996/clink-gizmos
MIT License
Copyright (c) 2023 Chris Antos
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the «Software»), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED «AS IS», WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
cmake
The CMake project manager uses the CMake lexer code for parsing CMake files
https://gitlab.kitware.com/cmake/cmake.git
CMake — Cross Platform Makefile Generator
Copyright 2000-2023 Kitware, Inc. and Contributors
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
-
Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer. -
Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution. -
Neither the name of Kitware, Inc. nor the names of Contributors
may be used to endorse or promote products derived from this
software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
«AS IS» AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
RSTParser
RSTParser is an open-source C++ library for parsing reStructuredText
https://github.com/vitaut-archive/rstparser
License
Copyright (c) 2013, Victor Zverovich
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
- Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer. - Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS «AS IS» AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
QtKeychain
QtKeychain provides the Axivion plugin with the means to securely store
and retrieve dashboard credentials.
https://github.com/frankosterfeld/qtkeychain
Distributed under the Modified BSD License
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
- Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer. - Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution. - The name of the author may not be used to
endorse or promote products derived from this software without
specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR «AS IS» AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Qt Creator app for Windows 10 – Learn how to download and install the Qt Creator 4.11.1 (64-bit) application on your Windows 10 PC for free. Complete integrated development environment (IDE) for application developers. Now, this Developer Tools app is available for PC Windows Vista64 / Windows 7 64 / Windows 8 64 / Windows 10 64.
Complete integrated development environment (IDE) for application developers
Table of Contents
Qt Creator 4.11.1 (64-bit) Overview
Qt Creator is a Developer Tools application like Emacs, Adobe XD, and Stencyl from The Qt Company. It has a simple and basic user interface, and most importantly, it is free to download. Qt Creator is an efficient software that is recommended by many Windows PC users.
Qt Creator is a very fast, small, compact and innovative Open Source Developer Tools for Windows PC. It is designed to be uncomplicated for beginners and powerful for professionals. This app has unique and interesting features, unlike some other Developer Tools apps. Qt Creator works with most Windows Operating System, including Windows Vista64 / Windows 7 64 / Windows 8 64 / Windows 10 64.
Although there are many popular Developer Tools software, most people download and install the Open Source version. However, don’t forget to update the programs periodically. You can get Qt Creator free and download its latest version for Windows Vista64 / Windows 7 64 / Windows 8 64 / Windows 10 64 PC from below.
Qt Creator 4.11.1 (64-bit) Technical Details
It’s better to know the app’s technical details and to have a knowledge background about the app. Therefore, you can find out if Qt Creator will work on your Windows device or not.
App Name: | Qt Creator |
Developer: | The Qt Company |
Version: | Qt Creator 4.11.1 (64-bit) LATEST |
Updated: | February, 6th 2020 |
Category | Developer Tools |
File Size: | 286 MB |
File Type: | EXE file |
Requirement: | PC/laptop/tablet running Windows (Windows Vista64 / Windows 7 64 / Windows 8 64 / Windows 10 64) |
License: | Open Source |
Download Qt Creator 4.11.1 (64-bit) (latest version) free for Windows 10 PC/laptop/tablet. Safe Download and Install from the official link!
Qt Creator download features:
- Qt Creator direct, free and safe download
- Latest version update
- Compatible with Windows 10
- Download Qt Creator for your PC or laptop
Qt Creator Setup Installer
Download & install the latest offline installer version of Qt Creator for Windows PC / laptop. It works with Windows Vista64 / Windows 7 64 / Windows 8 64 / Windows 10 64.
✔ Free & Safe Download for Windows PC/laptop – 286 MB
Safety (Virus) Test:
✔ Tested and is to download and install on your Windows Vista64 / Windows 7 64 / Windows 8 64 / Windows 10 64 device (PC/laptop/tablet).
What is New in the Qt Creator Latest Version?
✓ Compatibilities improvement for new Windows update.
✓ Fixes bugs.
How to download and install Qt Creator for Windows 10 PC/laptop
Now let’s just move to the next section to share the steps you have to follow to download Qt Creator for Windows PC. So here we go:
- Download the Qt Creator installer file from the link above.
- Save the downloaded file to your computer.
- Double-click on the downloaded Qt Creator installer file.
- Now, a smart screen might appear and ask for a confirmation.
- Click “Yes” to confirm.
- Finally, follow the installation instructions until you get a confirmation notification of a successful installation process.
So those are all the processes that you have to follow to download Qt Creator for Windows PC. Then let’s go on to the next section where we will discuss Qt Creator itself. So you can understand the application and its features. So here we go:
Top Features of Qt Creator for Windows PC
Qt Creator is one of the most popular Developer Tools alongside Postman, Notepad++, and PowerShell. This app has its advantages compared to other Developer Tools applications. Qt Creator is lightweight and easy to use, simple for beginners and powerful for professionals. Qt Creator application is free to download and offers easy-to-install, easy-to-use, secure, and reliable Developer Tools applications.
This application’s primary functions are comprehensive and go beyond the features offered by others that can be considered as its rivals.
- Qt Creator for PC – fast, reliable, and robust by The Qt Company.
- Qt Creator Free & Safe Download.
- Qt Creator latest version for the best experience.
- It works/compatible with almost all Windows versions, including Windows Vista64 / Windows 7 64 / Windows 8 64 / Windows 10 64.
- Free of Cost!
- User-friendly Interface.
- Easy to Use.
- Privacy and Security!
- Lightweight and consume low resources.
- Best for Developer Tools application.
- PC User’s choice!
How to uninstall Qt Creator in Windows PC?
Steps to uninstall Qt Creator in Windows 10 / Windows 8 / Windows 7 / Windows Vista
- Click the Windows Start menu.
- Locate and select the Control Panel menu, then select Programs.
- Under Programs, click the Uninstall a Program.
- Select Qt Creator and then right-click, select Uninstall/Change.
- Then click Yes to confirm the Qt Creator uninstallation process.
Steps to uninstall Qt Creator in Windows XP
- Click the Windows Start menu.
- Locate and select the Control Panel menu, then select Add or Remove Programs icon.
- Select the Qt Creator and then click Remove/Uninstall.
- Then click Yes to confirm the Qt Creator uninstallation process.
Steps to uninstall Qt Creator in Windows 95, 98, Me, NT, 2000
- Click the Windows Start menu.
- Locate and select the Control Panel menu, then double-click the Add/Remove Programs icon.
- Select the Qt Creator and then right-click, select Uninstall/Change.
- Then click Yes to confirm the Qt Creator uninstallation process.
Best Qt Creator Alternative Apps for Windows
Isn’t Qt Creator what you were looking for? We prepared a list of alternatives below!
- Postman
- Notepad++
- PowerShell
- HeidiSQL
- StarUML
Postman, Notepad++, and PowerShell is the strong competitor of Qt Creator. Otherwise, HeidiSQL and StarUML also quite good as the alternative of this software. There are also other similar apps such as Stencyl, Adobe XD, and Emacs that also need to try if you want to find the best alternative of Qt Creator.
In Conclusion
The Qt Creator for Windows PC is unquestionably the best Developer Tools that you can find nowadays. It also is the most reliable when it comes to performance and stability. You can find that out for yourself. That is why a lot of PC users recommend this app.
Get superb and impressive experience using this Qt Creator application developed by The Qt Company. Qt Creator nowadays are already getting better each time.
If you have some questions related to this app, feel free to leave your queries in the comment section. Or you can share with us your experience when using this Qt Creator on your Windows 10 PC. And if you know other people who want to experience Qt Creator for Windows PC, you can share this article to help them. Enjoy using Qt Creator for Windows PC.
Find other interesting articles that will help you how to download Postman for Windows 10 PC, install Notepad++ for Windows 10, PowerShell review, or about best HeidiSQL alternative apps for Windows 10.
Qt Creator FAQ (Frequently Asked Questions)
Q: What is Qt Creator for PC?
A: For more information about this app, please go to the developer link on the above of this page.
Q: Is Qt Creator free? If not, how much does it price to download this app?
A: Absolutely no cost! You can download this app from official websites for free by this website—any extra details about the license you can found on the owner’s websites.
Q: How do I access the free Qt Creator download for Windows PC?
A: It is easy! Just click the free Qt Creator download button in the above of this page. Clicking the download button will start the installer to download Qt Creator free for a PC/laptop.
Q: Is this Qt Creator will typically run on any Windows?
A: Yes! The Qt Creator for PC will typically work on most recent Windows operating systems, including Windows Vista64 / Windows 7 64 / Windows 8 64 / Windows 10 64.
Q: What’s the difference between 64-bit and 32-bit versions of Qt Creator?
A: The Qt Creator 64-bit version was specially designed for 64-bit Windows Operating Systems and performed much better on those. The Qt Creator 32-bit version was initially intended for 32-bit Windows Operating Systems, but it can also run on 64-bit Windows Operating Systems.
Q: What’s the importance of downloading the latest version of Qt Creator?
A: We recommend downloading the latest version of Qt Creator because it has the most recent updates, which improves the quality of the application.
Disclaimer
Qt Creator is an application that builds by The Qt Company. All trademarks, product names, company names, and logos mentioned here are their respective owners’ property. This site (autotechint.com) is not affiliated with them directly. All information about applications, programs, or games on this website has been found in open sources on the Internet.
We don’t host or store Qt Creator on our servers. Downloads are done through the Official Site. We are firmly against piracy, and we do not support any sign of piracy. If you think that the application you own the copyrights is listed on our website and want to remove it, please contact us.
We are always compliant with DMCA regulations and respect the application owners. We are happy to work with you. Please find the DMCA / Removal Request page below.