Reference
The following topics contain reference information about using Qt Creator and the integrated tools.
Options for starting Qt Creator from the command line. | |
Wizard types and JSON wizard format. | |
Answers to some frequently asked questions about Qt Creator. | |
Qt Creator terms and concepts. | |
Default keyboard shortcuts. | |
Known issues in Qt Creator version 14.0.2. | |
Licenses and third-party components in Qt Creator. | |
Configure CMake and set up compilers, debuggers, devices, Qt versions, and kits from the command line. | |
Qt support sites and other useful sites. | |
Version control systems that you can use from Qt Creator. |
Analyzers
Use integrated code analysis tools to improve your C++ or QML code.
Visualize Chrome trace events generated in Chrome Trace Format (CTF). | |
Detect memory leaks with Heob. | |
Run static checks on the QML and JavaScript code in your project to find common problems. | |
Analyze the CPU and memory usage of an application on Linux desktop and embedded devices. | |
Improve the performance of QML applications. |
Build Systems
When you create projects, you can choose the build system to use for building the project: CMake, qmake, Meson, or Qbs. qmake is installed and configured when you install Qt. To use one of the other supported build systems, you need to set it up.
With Autotools, you can create a portable, complete, and self-contained GNU Build System from simple instructions. | |
CMake is an alternative to qmake for automating the generation of build systems. | |
The experimental Conan plugin integrates the Conan package manager. | |
IncrediBuild decreases the time it takes to build C++ code. | |
Use Meson to build native desktop applications. | |
The Nimble package manager uses the Nim compiler to generate Nim application executables for the desktop platforms. | |
Qbs is an all-in-one build tool that generates a build graph from a high-level project description (like qmake or CMake do) and executes the commands in the low-level build graph (like make does). | |
The experimental vcpkg plugin integrates the vcpkg C/C++ package manager. |
Build Configurations
Build configurations have everything you need to compile the sources into binaries. Build configurations use the tools and settings defined in their corresponding kit.
Settings for building applications with CMake. | |
Examples of supported CMake presets. | |
Settings for building applications with the Conan package manager. | |
Build and clean steps for Incredibuild. | |
Settings for building applications with Meson. | |
Settings for building applications with Qbs. | |
Settings for building applications with qmake. |
Debuggers
Set up and use debuggers to debug executable binary files, as well as QML, Java, and Python source code.
Load, customize, and add debugging helpers. | |
Debug JavaScript functions, execute JavaScript expressions to get information about the state of the UI, and inspect QML properties and JavaScript variables, as well as change their values temporarily at runtime. | |
Summary of supported debugger versions. | |
Solve problems that you might encounter while debugging. |
Debugger Views
Inspect the state of your application while debugging in the Debug mode.
Inspect the state of your application while debugging. | |
Troubleshoot the debugger. | |
Compute values of arithmetic expressions or function calls. | |
Inspect local variables and function parameters. | |
View the current state of peripheral devices, such as a mouse, keyboard, display, printer, or USB drive. | |
Set breakpoints to interrupt the application. | |
View the nested function calls leading to the current position as a call stack trace. | |
View disassembled code for the current function. | |
View information about the modules included in a debugged application. | |
View source files included in a debugged project. | |
View the threads currently active in a multi-threaded application. | |
View the current state of general-purpose and special-purpose CPU registers. |
Devices
Connect devices to the computer to run, debug, and analyze applications built for them from Qt Creator. When you install Qt for a target platform, such as Android or QNX, the build and run configurations for the development targets might be set up automatically in Qt Creator.
Set up the toolchain for building applications for Android devices. | |
Create kits to use Bare Metal toolchains installed on the computer to build applications for and run and debug them on connected Bare Metal devices. | |
Connect Boot to Qt devices to the computer to run, debug, and analyze applications built for them from Qt Creator. | |
Connect MCU devices to the computer to run and debug applications on them. | |
Connect generic Linux devices to the computer to run, debug, and analyze applications built for them from Qt Creator. | |
Connect iOS devices to your local machine with a USB cable to run applications on them. |
Deploy Configurations
Deploy configurations handle the packaging of the application as an executable and copying it to a location you want to run the executable at. The files can be copied to a location in the file system of the computer or a device.
Create Application Packages (APK) or Android App Bundles (AAB) to install and run on devices or to upload to the Google Play store. | |
Copy application files to Boot to Qt devices. | |
Copy application files to QNX Neutrino devices. | |
Copy application files to generic remote Linux devices or create a tarball. |
Run Configurations
Run configurations start the application in the location where the deploy configuration copied it. By default, when you select Run, Qt Creator builds the project, deploys it to the device defined in the kit, and runs it there. If you did not make changes to the project since you last built and deployed it, Qt Creator simply runs it again.
Settings for running applications on Android devices. | |
Settings for running applications on Boot to Qt devices. | |
Settings for running applications on desktop device types. | |
Settings for running Qt for Python applications. | |
Settings for running applications on Linux-based devices. | |
Settings for running Qt Quick UI Prototype projects (.qmlproject). | |
Settings for running applications on Linux-based devices. |
Editors
When you open files, Qt Creator chooses a suitable editor according to the file type.
Summary of quick fixes for C++ code. | |
Offers code editing services for C++. | |
Edit and navigate code and other resources in your projects. | |
Supported Vim modes and emulated commands. | |
Get code completion, highlighting of the symbol under cursor, and jumping to the symbol definition in the editor for other programming languages besides C++, as well as diagnostics. | |
Create Universal Modeling Language (UML) style models with structured and behavioral diagrams. | |
Summary of quick fixes for QML code. | |
Edit state chart (.scxml) files. |
Platforms
You can install and run Qt Creator on several operating systems to create applications for multiple desktop, embedded, and mobile device platforms.
Requirements for operating systems that you can install and run Qt Creator on. | |
Guidelines for developing usable applications for mobile devices. | |
Summary of development and target platforms. |
Preferences
You can set preferences that apply globally to all projects and override them for particular projects.
Create a connection to an Axivion dashboard server. | |
Format source code with Artistic Style, ClangFormat, or Uncrustify. | |
Set indentation for Vim-style editing and map vim commands to Qt Creator functions. | |
Add and change locator filters. | |
Set Nim code style and paths to tools. | |
Set preferences for Qbs and Qbs profiles. | |
Set QML code style. | |
Set preferences for recording screens with FFmpeg. | |
Customize the handling of tests, test frameworks, and test tools. | |
Add keywords for listing to-do entries. |
Analyzer
Preferences for code analysis tools.
Set preferences for Clang-Tidy and Clazy. | |
Set preferences for Valgrind Callgrind. | |
Set preferences for Valgrind Memcheck. |
C++
Preferences for editing C++ code.
Set global code style for C++ files. | |
Sets global preferences for the clangd code model. | |
Sets global preferences for the C++ code model. | |
Set global preferences for C++ quick fixes. |
Debugger
Preferences for debugging.
Manage the CDB process. | |
Add the Microsoft Symbol Server to the symbol search path of the debugger. | |
Manage the GDB process. | |
Customize debug views and map source paths. |
Kits
Preferences for build and run kits.
Lists the registered compilers. You can add custom compilers to the list. | |
Set kit preferences. A kit consists of a set of values that define one environment, such as a device, toolchain, Qt version, and debugger command to use. |
Text Editor
Preferences for the behavior and appearance of text and code editors.
Set preferences for indentation, typing, and file encoding in the text editor. | |
Set preferences for code completion and inserting matching characters in the text editor. | |
Set the font preferences and apply color schemes for syntax highlighting, diff editor, and code analysis results. | |
Add, change, and remove snippets in the snippet editor. |
UI Design
You can use a visual editor, Qt Widgets Designer, for designing widget-based UIs in the Design mode. For Qt Quick UIs, use a separate visual editor, Qt Design Studio, or the Edit mode.
Adding widgets to Qt Widgets Designer by creating plugins that extend Qt applications. | |
Converting a project that has a .qmlproject file to one that has a .pro file. | |
A visual editor for QML files (.qml) and Qt Design Studio UI files (.ui.qml). | |
A visual editor for Qt Widgets. | |
Limitations of Qt Design Studio UI files (.ui.qml). | |
Using C++ plugins to expose custom components to Qt Quick applications. |
Views
When you switch modes or trigger actions, Qt Creator opens views for viewing output and organizing project contents.
Output Views
You can view output from several sources, such as a list of errors and warnings encountered during a build, detailed output from the compiler, status of a program when it is executed, debug output, or search results.
Displays the status of a program when you execute it, and the debug output. | |
Shows all output from the compiler. | |
Lists issues from different sources. | |
Search through projects, files on a file system or the currently open files and view search results. | |
View Squish test, runner, and server logs. | |
Opens a terminal. | |
View test results. | |
Lists to-do keywords from project files. |
Sidebar Views
In some modes, you can use a left and right sidebar to organize different views into project contents. Only views that are relevant to the mode you are working in are available in it.
Shows information about incoming and outgoing function calls from a language server. | |
Shows the class hierarchy of the currently open projects. | |
Shows all the files in the current directory. | |
Shows the files that the current file includes and those that include the current file. | |
Shows currently open files. | |
Shows an overview of defined types and other symbols, as well as their properties and hierarchy in a source file. | |
Shows a list of projects in a project tree. The project tree has a list of all projects open in the current session. For each project, the tree visualizes the build system structure of the project and lists all files that are part of the project. | |
Shows the base classes and derived classes of a class. |
© 2024 The Qt Company Ltd. Documentation contributions included herein are the copyrights of their respective owners. The documentation provided herein is licensed under the terms of the GNU Free Documentation License version 1.3 as published by the Free Software Foundation. Qt and respective logos are trademarks of The Qt Company Ltd in Finland and/or other countries worldwide. All other trademarks are property of their respective owners.