1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
|
// Copyright (C) 2023 The Qt Company Ltd.
// SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GFDL-1.3-no-invariants-only
// **********************************************************************
// NOTE: the sections are not ordered by their logical order to avoid
// reshuffling the file each time the index order changes (i.e., often).
// Run the fixnavi.pl script to adjust the links to the index order.
// **********************************************************************
/*!
\previouspage creator-version-control.html
\page creator-configuring-projects.html
\nextpage creator-project-managing-sessions.html
\title Configuring Projects
When you install Qt for a development or target platform, such as Linux,
\macos, Windows, Android or QNX, \l{https://www.qt.io/download-qt-installer}
{\QOI} creates \l{glossary-buildandrun-kit}{kits} for the development targets.
Select the kits to use for a project in the \uicontrol {Configure Projects}
view when you open the project for the first time. At least one kit must be
active.
To maintain the list of active kits for a currently open project, switch to
the \uicontrol Projects mode by pressing \key Ctrl+5.
\image qtcreator-projects-kits.webp {Sidebar in the Projects mode}
To specify build or run settings for a kit, select \uicontrol Build or
\uicontrol Run below the kit name.
\section1 Specifying Build Settings
\image qtcreator-build-configurations.png {Build configurations}
Different build configurations allow you to quickly switch between
different build settings. By default, \QC creates the following
configurations:
\list
\li Debug
\li Release
\li Profile
\endlist
A debug build has debug symbols that you need for debugging the application
but that you can leave out from the release version. Generally, you use the
debug configuration for testing and the release configuration for creating
the final installation binary package.
If you selected CMake as the build system for the project, you can
use a \e {minimum size release} build configuration to create the
final installation binary package. It is a release build that makes the size
of the binary package as small as possible, even if this makes the
application slower.
A profile build (which is called \e {release with debug information}
when using CMake) is an optimized release build that is delivered
with separate debug information. It is best suited for analyzing
applications.
\section1 Specifying Run Settings
The run settings to specify depend on the type of the project and on the
\l{kits-tab}{Run device} that you select for the kit.
\QC automatically creates deploy and run configurations for your project.
\image qtcreator-settings-run-desktop.webp {Run Settings}
To prevent \QC from automatically creating run configurations, select
\preferences > \uicontrol {Build & Run}, and then deselect the
\uicontrol {Create suitable run configurations automatically} check box.
\section1 Overriding Global Preferences
In \uicontrol {Project Settings}, you can override global preferences for
the project:
\list
\li \l{Link projects to Axivion dashboards}{Axivion}
\li \l{Specify clangd settings}{Clangd}
\li \l{Speficy Clang tools settings}{Clang Tools}
\li \l{Specify code style}{C++ Code Style}
\li \l{Set C++ file naming preferences}{C++ File Naming}
\li \l{Specify dependencies}{Dependencies}
\li \l{Document code}{Documentation Comments}
\li \l{Specify editor settings}{Editor}
\li \l{Specify the environment for projects}{Environment}
\li \l{Configure language server workspace}{Language Server}
\li \l{Specify settings for quick fixes}{Quick Fixes}
\li \l{Exclude files from to-do lists}{To-Do} (experimental)
\endlist
If you have multiple projects open in \QC, select the project to configure
in \uicontrol {Active Project}.
\sa {Activate kits for a project}, {Configure projects for building},
{Configure projects for running}, {Open projects},
{Activate custom output parsers}
*/
/*!
\page creator-how-to-activate-kits.html
\previouspage creator-how-tos.html
\ingroup creator-how-to-projects-configure
\title Activate kits for a project
The \uicontrol {Build & Run} section of the \uicontrol Projects mode sidebar
lists the kits that are compatible with your project. To activate one or more
kits, click them.
\image qtcreator-projects-kits.webp {List of kits in Projects mode sidebar}
The list displays kits from \preferences >
\uicontrol Kits. Warning and error icons indicate that the kit configuration
is not suitable for the project type. To view the warning and error messages,
move the mouse pointer over the kit name.
\section1 Manage kits
To modify kit configuration or to \l{Add kits}{add kits} to the list or to
remove them from it, select \uicontrol {Manage Kits}.
Each kit consists of a set of values that define one environment, such as a
\l{glossary-device}{device}, \l{Add compilers}{compiler},
\l{Add debuggers}{debugger}, and \l{Add Qt versions}{Qt version}, as well
as steps for building, deploying, and running applications.
To copy the build, deploy, and run steps from another kit, select
\uicontrol {Copy Steps from Another Kit} in the context menu.
To deactivate a kit, select \uicontrol {Disable Kit for Project} in the
context menu.
\note Deactivating a kit removes all custom build and run settings for the
kit.
To import an existing build for the project, select
\uicontrol {Import Existing Build}.
\section1 Copy custom settings from vanished targets
\QC creates a list of \uicontrol {Vanished Targets} to save project-specific
settings, such as custom build flags or run configuration arguments, that
would disappear if \QOI removes the corresponding kits when you update your
Qt installation.
\image qtcreator-projects-vanished-targets.webp {Vanished Targets in Projects}
Go to one of the following options in the context menu to restore the
project's settings:
\list
\li \uicontrol {Create a New Kit} creates a new kit with the same name
for the same device type, with the original build, deploy, and run
steps. Other kit settings are not restored.
\li \uicontrol {Copy Steps to Another Kit} copies the build, deploy, and
run steps to another kit.
\endlist
To remove vanished targets, go to \uicontrol {Remove Vanished Target} or
\uicontrol {Remove All Vanished Targets} in the context menu.
\note Since version 13.0, \QC does not create \e {replacement kits}, but you
might still see them listed for existing projects. You can copy the build,
deploy, and run steps from them to other kits.
\sa {Add kits}, {Configuring Projects}, {kits-tab}{Kits}
*/
|
