QT
SOFTWARE

Qt Creator

A cross-platform IDE for Qt, C++ and QML that organizes compilers, Qt versions, debuggers and target devices into reproducible Kits.

WindowsmacOSLinuxGPL-3.0 with Qt Company GPL Exception or commercial terms

What Qt Creator is for

Qt Creator combines a code editor, project configuration, debugger and device management workflow for Qt, C++ and QML projects. It can work with CMake, qmake and other build systems, but the IDE itself does not automatically include every Qt library or compiler needed by a project.

Treat a Kit as a complete toolchain

A usable Kit joins a target device, compiler, debugger, Qt version and build tool. If one path points to a different architecture or an old installation, configuration may appear to succeed while the build or run step fails. Keep Debug and Release build directories separate and record the toolchain for each project.

Keep project configuration portable

User settings often contain absolute paths, SDK locations and device details. Share the project files and dependency notes rather than copying a personal configuration directory. Before a long migration, create a small test build and confirm the generated executable on the target platform.

Maintenance note

This page covers Qt Creator, Kit configuration, CMake projects and first-build boundaries. Content review date: 2026-08-23.

SAVE TO CLOUD

Save to your cloud drive

Open the cloud drive to get the file directly, or save it for convenient access on another device.

Links checked 2026-08-06
Save first, access when you need itOn desktop, scan with the matching cloud-drive app. On mobile, tap the save button.
GUIDE

Qt Creator installation, Kit configuration and first build

Build a small test project first, then verify that the Qt version, compiler, debugger and target device form a compatible Kit.

Before you start

  • Decide whether the target is desktop, Android, embedded or another device class because each requires a different SDK and toolchain.
  • Prepare a matching compiler, debugger and Qt version; a standalone IDE package may not include the complete Qt development stack.
  • Identify whether the project uses CMake, qmake, Qbs or another build system.
01

Installation steps

  1. 01

    Choose a full Qt package or standalone IDE

    New users can install a Qt package with the required modules and IDE; existing toolchains can use the standalone IDE and register components manually.

  2. 02

    Check Qt versions and compilers

    Open the Kits settings and verify that Qt Versions, Compilers and Debuggers point to real executables with matching architecture.

  3. 03

    Create a compatible Kit

    Combine the device, compiler, debugger, Qt version and build tool. A warning icon usually identifies a missing path or incompatible component.

02

Quick start

  1. 01

    Open or create a project

    Choose a clear project directory and select the correct CMakeLists file or project file. Do not use a build directory as the source directory.

  2. 02

    Select a build configuration

    Enable a compatible Kit, then keep Debug and Release configurations in separate build directories so cached settings do not mix.

  3. 03

    Build and run a small target

    Read the first compiler or configuration error in Issues and Compile Output, fix it, and run the generated target only after the build completes.

Usage tips

  • Do not copy personal Kit settings between computers because they commonly contain machine-specific absolute paths.
  • Keep SDKs, compilers and Qt modules versioned with the project notes so a future rebuild can reproduce the environment.
  • When code completion is wrong, check the active Kit and code model before deleting project files or reinstalling the IDE.
Troubleshooting and uninstall

Why is no Kit available in Configure Project?

Confirm that a Qt version and compiler are installed, then add their actual paths in Preferences. A standalone IDE does not provide a complete Qt SDK by itself.

Why does the project build but not run?

Check Run Settings, the executable path, working directory, environment variables and target device. Confirm that the selected configuration produced the expected binary.

  1. Back up source and dependency notesKeep source files, project configuration, module requirements and a small reproducible build before removing the IDE.
  2. Remove the IDE and optional componentsUninstall through the operating system or Qt maintenance tool, then remove SDKs and caches only after confirming another build environment works.
FAQ

Frequently asked questions

Does installing Qt Creator install Qt itself?

Not always. The IDE, Qt libraries, compiler, debugger and SDK are separate pieces unless a complete package selected them together.

What does a Kit represent?

A Kit is the compatible combination of device, compiler, debugger, Qt version and build tool used to configure and build a project.

Why should Debug and Release use different directories?

They produce different generated files and compiler settings. Separate directories avoid stale cache values and make it easier to reproduce or clean one configuration.