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
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
|
/****************************************************************************
**
** Copyright (C) 2019 The Qt Company Ltd.
** Contact: https://www.qt.io/licensing/
**
** This file is part of the Qt Creator documentation.
**
** Commercial License Usage
** Licensees holding valid commercial Qt licenses may use this file in
** accordance with the commercial license agreement provided with the
** Software or, alternatively, in accordance with the terms contained in
** a written agreement between you and The Qt Company. For licensing terms
** and conditions see https://www.qt.io/terms-conditions. For further
** information use the contact form at https://www.qt.io/contact-us.
**
** GNU Free Documentation License Usage
** Alternatively, this file may be used under the terms of the GNU Free
** Documentation License version 1.3 as published by the Free Software
** Foundation and appearing in the file included in the packaging of
** this file. Please review the following information to ensure
** the GNU Free Documentation License version 1.3 requirements
** will be met: https://www.gnu.org/licenses/fdl-1.3.html.
**
****************************************************************************/
// **********************************************************************
// 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-configuring-projects.html
\page creator-targets.html
\nextpage creator-project-qmake.html
\title Adding Kits
\QC groups settings used for building and running projects as kits
to make cross-platform and cross-configuration development easier. Each kit
consists of a set of values that define one environment, such as a
\l{glossary-device}{device}, compiler, Qt version, and debugger command
to use, and some metadata, such as an icon and a name for the kit. Once
you have defined kits, you can select them to build and run projects.
\QC supports development for the desktop and for the following types of
devices:
\list
\li Android Device
\li Bare Metal Device
\li Boot2Qt Device (commercial only)
\li \l {Emulator}{Boot2Qt Emulator Device} (commercial only)
\li Generic Linux Device
\li iOS Device
\li iOS Simulator
\li QNX Device
\li Windows Phone
\li Windows Phone Emulator
\li Windows Runtime (local)
\endlist
\section1 Filtering Kit Settings
Typically, only a subset of the kit settings is relevant for a particular
setup. Therefore, \QC plugins register sets of relevant settings that you
can view and modify in \uicontrol Tools > \uicontrol Options >
\uicontrol Kits >. For example, if you use CMake to build all your projects,
you can hide Qbs and qmake settings by default.
To hide and show settings in the \uicontrol Kits tab for the
current kit, select \uicontrol {Settings Filter}. To view and
modify the settings displayed when you add a new kit, select
\uicontrol {Default Settings Filter}.
\section1 Specifying Kit Settings
To add kits:
\list 1
\li Select \uicontrol Tools > \uicontrol Options > \uicontrol Kits >
\uicontrol Add.
\image qtcreator-kits.png
To clone the selected kit, select \uicontrol Clone.
\li In the \uicontrol Name column, enter a name for the kit.
\li Select the \inlineimage qtcreator-desktopdevice-button.png
button to select an image to use as an icon for the kit.
\li In the \uicontrol {File system name} field, enter a name for the kit
to use as a part of directory names. This value is used for the
\e CurrentKit:FileSystemName variable, which determines the name of
the shadow build directory, for example.
\li In the \uicontrol{Device type} field, select the type of the device.
Double-click the icon next to the field to select the image that is
displayed in the kit selector for this kit. You can use any
image in a supported file format (for example, PNG). The image is
scaled to the size 64x64 pixels. For example, using the compiler
logo as an icon allows you to easily see, which compiler is used to
build the project for the selected kit.
\li In the \uicontrol Device field, select a device.
\li In the \uicontrol Sysroot field, specify the directory where the device
image is located. If you are not cross-compiling, leave this field
empty.
\li In the \uicontrol {Emulator skin} field, select the skin to use for
the \l {Emulator}{Boot2Qt Emulator Device}.
\li In the \uicontrol {Compiler} field, select the C or C++ compiler
that you use to build the project. You can add compilers to the list
if they are installed on the development PC, but were not detected
automatically. For more information, see \l{Adding Compilers}.
This setting is used to tell the code model which compiler is used.
If your project type and build tool support it, \QC also tells the
build tool to use this compiler for building the project.
\li In the \uicontrol Environment field, select \uicontrol Change to modify
environment variable values for build environments in
the \uicontrol {Edit Environment Changes} dialog. For more information
about how to add and remove variable values, see \l{Batch Editing}.
\li Select the \uicontrol {Force UTF-8 MSVC compiler output} check box
to either switch the language of MSVC to English or to keep the
language setting and just force UTF-8 output, depending on the
MSVC compiler used.
\li In the \uicontrol Debugger field, select the debugger to debug the project
on the target platform. \QC automatically detects available
debuggers and displays a suitable debugger in the field. You can
add debuggers to the list. For more information, see
\l{Adding Debuggers}.
For Android kits, the \uicontrol {Android GDB server} field will
display the path to GDB server executable.
\li In the \uicontrol {Qt version} field, select the Qt version to use for
building the project. You can add Qt versions to the list if they
are installed on the development PC, but were not detected
automatically. For more information, see \l{Adding Qt Versions}.
\QC checks the directories listed in the \c{PATH} environment
variable for the qmake executable. If a qmake executable is found,
it is referred to as \b{Qt in PATH} and selected as the Qt
version to use for the \uicontrol Desktop kit that is created by default.
\li In the \uicontrol {Qt mkspec} field, specify the name of the mkspec
configuration that should be used by qmake. If you leave this field
empty, the default mkspec of the selected Qt version is used.
\li In the \uicontrol {Additional Qbs profile settings} field, select
\uicontrol Change to add settings to Qbs build profiles. For more
information, see \l {Editing Qbs Profiles}.
\li In the \uicontrol {CMake Tool} field, select the CMake tool to use
for building the project. Select \uicontrol Manage to add installed
CMake tools to the list. For more information, see
\l{Adding CMake Tools}.
\li In the \uicontrol {CMake generator} field, select \uicontrol Change
to edit the CMake
Generator to use for producing project files. Only the generators
with names beginning with the string \uicontrol CodeBlocks produce
all the necessary data for the \QC code model. \QC displays a
warning if you select a generator that is not supported.
\li In the \uicontrol {CMake configuration} field, select
\uicontrol Change to edit the variables of the CMake configuration
for the kit.
\endlist
\QC uses the \e {default kit} if it does not have enough information to
choose the kit to use. To set the selected kit as the default kit,
select \uicontrol {Make Default}.
\include creator-projects-cmake-building.qdocinc cmake ninja
\section1 Editing Qbs Profiles
To view the Qbs profile associated with the kit, select \uicontrol Tools >
\uicontrol Options > \uicontrol Qbs > \uicontrol Profiles.
\image creator-qbs-profiles.png "Qbs Profiles tab"
You can add keys and values to the profile or remove them from it, as well
as modify existing values. For a list of available keys and values, see
\l{http://doc.qt.io/qbs/list-of-modules.html}{List of Modules} in the Qbs
Manual.
To edit the Qbs profile associated with the kit:
\list 1
\li Select \uicontrol Change next to the
\uicontrol {Additional Qbs Profile Settings} field to open the
\uicontrol {Custom Properties} dialog.
\image qtcreator-qbs-profile-settings.png "Custom Properties dialog"
\li Double-click an empty cell in the \uicontrol Key column to specify
the key to add or modify as: \c <module_name>.<property_name>.
\li Double-click the cell on the same row in the \uicontrol Value column
to specify a value as a JSON literal.
\li Select \uicontrol Add to add the key-value pair.
\li Click \uicontrol OK.
\endlist
To modify an existing value, double-click it in the \uicontrol Value field.
To remove the selected property, select \uicontrol Remove.
*/
|
