feedc0de/qt-creator
1
0
Fork 0
forked from qt-creator/qt-creator
Code Pull Requests Activity

Device type + tool chain + other settings -> Kit

Browse Source 
We called that "Target" before

Change-Id: Ie0d673c643947c26ac2706907f6250fc1739388a
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@nokia.com>
This commit is contained in:
Eike Ziller
2012-09-03 17:50:37 +02:00
parent fb59a39a78
commit 328d205b62
44 changed files with 201 additions and 191 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
doc/src/overview/creator-deployment-overview.qdoc
View File

@@ -40,7 +40,7 @@
\o \l{Deploying Applications to Linux-Based Devices}
When you deploy the application on a Linux-based device target, such
When you deploy the application on a Linux-based device, such
as \gui {Embedded Linux}, \gui Harmattan, or \gui{Maemo5}, \QC
copies the application files to the connected device. You
can test and debug the application on the device.
@@ -48,14 +48,14 @@
Maemo 5 devices.
\o \l{Deploying Applications to QNX Devices}
When you deploy the application on the \gui{QNX} target, depending
When you deploy the application on a \gui{QNX} device, depending
on your target device, \QC either generates a BAR package in the
build directory and deploys it to the connected device, or copies
the application files to the connected device. You can test and
debug the application on the device.
\o \l{Deploying Applications to Android Devices}
When you deploy the application on the Android target, \QC copies
When you deploy the application on an Android device, \QC copies
the application files to the device. In addition, you can determine
the Qt libraries to use.
\endlist
@@ -68,7 +68,7 @@
When you are ready to publish the application on a publishing
channel, you must make sure that the installation file meets the
requirements for publishing and installing applications to the
target devices.
targeted devices.
\endlist
*/

2
doc/src/overview/creator-getting-started.qdoc
View File

@@ -49,7 +49,7 @@
with the parts of the user interface, go to \l{User Interface}.
\o \bold {\l{Building and Running an Example}}
To check that \l{glossary-development-target}{targets} were
To check that \l{glossary-buildandrun-kit}{kits} for building and running were
successfully installed as part of the \QSDK installation, open
an example application and run it. If you have not done so
before, go to \l{Building and Running an Example}.

34
doc/src/overview/creator-glossary.qdoc
View File

@@ -43,7 +43,8 @@
into binaries. Different build configurations allow you to
quickly build the project for different purposes.
By default, \QC creates \e {debug build} and \e {release build}
configurations for each \e target. A debug build contains
configurations for each \l{glossary-buildandrun-kit}{kit} defined for your project.
A debug build contains
additional 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
@@ -79,6 +80,15 @@
copied to a location in the file system of the development PC or
a mobile device.
\row
\o Kit
\target glossary-buildandrun-kit
\o \QC groups build and run specific settings as kits to make
cross-platform development easier. Each kit consists of a set
of values that define one environment, such as a device,
tool chain, Qt version, and debugger command to use. Configure kits at
\gui {Tools > Options > Build & Run > Kits}.
\row
\o Mode
\target glossary-mode
@@ -102,14 +112,15 @@
\target glossary-project-qt
\o \QC allows you to have multiple versions of Qt installed on your
development PC and use different versions to build your projects
for different \e targets.
for different purposes.
\row
\o Run configuration
\target glossary-run-config
\o Starts the application in the location where it was copied by
the \e {deploy configuration}. By default, when you run a
project, \QC builds it, deploys it to the selected \e target,
project, \QC builds it, deploys it to the device specified in the selected
\l{glossary-buildandrun-kit}{kit},
and runs it there. However, if you have not made any changes to
the project since you last built and deployed it, \QC simply
runs it again.
@@ -126,23 +137,6 @@
if you need many build configurations for a single set of
source files.
\row
\o Target
\target glossary-development-target
\o \QC groups platform specific settings as targets to make
cross-platform development easier. Each target consists of a set
of values that define one environment, such as a device,
tool chain, Qt version, and debugger command to use.
\row
\o Tool chain
\target glossary-tool-chain
\o Specifies a compiler and a debugger and other necessary
tools for building an application for a particular \e target.
\QC tries to detect the tool chains that are available on your
system. You can manually add tool chains that are not detected
automatically.
\endtable
*/

2
doc/src/overview/creator-issues.qdoc
View File

@@ -107,7 +107,7 @@
\if defined(qcmanual)
\o On Windows, you must create projects for Maemo 5 and Harmattan
targets on the same partition where you installed \QSDK, \QC, and
device types on the same partition where you installed \QSDK, \QC, and
MADDE.
\endif

3
doc/src/overview/creator-mobile-targets.qdoc
View File

@@ -32,7 +32,8 @@
\title Connecting Mobile Targets
You can connect mobile devices to the development PC to build, run, debug,
and analyze applications on them from \QC. When you install mobile targets
and analyze applications on them from \QC. When you install
\l{glossary-buildandrun-kit}{kits} for building and running on mobile targets
as part of the \QSDK, the build and run settings for the target devices are
set up automatically in \QC. However, \QSDK does not contain a tool chain
for building applications for embedded Linux devices.

5
doc/src/overview/creator-overview.qdoc
View File

@@ -87,9 +87,10 @@
and commands used to build the project.
\QC provides support for building, running, and deploying Qt
applications for desktop environment and mobile devices. Build,
applications for desktop environment and mobile devices.
\l{glossary-buildandrun-kit}{Kits}, build,
run, and deployment settings allow you to quickly switch between
targets.
different setups and targets.
For more information, see \l{Building and Running}.
\o \bold {\l{Debugging and Analyzing}}