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

27
doc/src/debugger/creator-debugger-setup.qdoc
View File

@@ -32,10 +32,10 @@
\title Setting Up Debugger
The main debugger settings are associated with the build
\l{glossary-development-target}{target} of your project. To specify the
debugger and compiler to use for each build target, select \gui Tools >
\gui Options > \gui {Build and Run} > \gui Targets.
The main debugger settings are associated with the
\l{glossary-buildandrun-kit}{kit} you build and run your project with. To specify the
debugger and compiler to use for each kit, select \gui Tools >
\gui Options > \gui {Build and Run} > \gui Kits.
You need to set up the debugger only if the automatic setup
fails, because the native debugger is missing (as is usually the
@@ -45,8 +45,9 @@
want to use a locally installed replacement instead).
\note If you need to change the debugger to use for an automatically
detected target, you can \gui{Clone} the target and change the parameters in
the clone. Make sure to select the cloned target for your project.
detected \l{glossary-buildandrun-kit}{kit},
you can \gui{Clone} the kit and change the parameters in
the clone. Make sure to select the cloned kit for your project.
\note To use the debugging tools for Windows, you must install them
and add the Symbol Server provided by Microsoft to the symbol search
@@ -54,7 +55,7 @@
Server in Windows}.
\note To use the Free Software Foundation (FSF) version of GDB on
Mac OS, you must sign it and modify your target settings.
Mac OS, you must sign it and modify your \l{glossary-buildandrun-kit}{kit} settings.
This section explains the options you have for debugging C++ code
and provides installation notes for the supported native debuggers.
@@ -185,8 +186,7 @@
\o On Linux and Windows, use the Python-enabled GDB versions that
are installed when you install \QC and Qt SDK. On Mac OS X,
use the GDB provided with Xcode.
For a custom \l{glossary-development-target}{target}, you can
build your own Python-enabled GDB. Follow the instructions in
You can also build your own Python-enabled GDB. Follow the instructions in
\l{http://developer.qt.nokia.com/wiki/QtCreatorBuildGdb}
{Building GDB}.
@@ -234,7 +234,7 @@
supports Python from
\l{ftp://ftp.qt.nokia.com/misc/gdb/7.2/gdb72_mac_platform.tar.bz2}.
To use FSF GDB on Mac OS, you must sign it and add it to the \QC
targets. For more information, see
\l{glossary-buildandrun-kit}{kits}. For more information, see
\l{Setting up FSF GDB for Mac OS}.
\note The Mac OS X Snow Leopard (10.6) has a bug that might cause the
@@ -272,7 +272,8 @@
\section1 Setting up FSF GDB for Mac OS
To use FSF GDB on Mac OS, you must sign it and add it to the \QC targets.
To use FSF GDB on Mac OS, you must sign it and add it to the \QC
\l{glossary-buildandrun-kit}{kits}.
\list 1
@@ -313,13 +314,13 @@
\endcode
\o In \QC, select \gui {Qt Creator > Preferences > Build & Run >
Targets} > \gui Add to create a build target that uses FSF GDB.
Kits} > \gui Add to create a kit that uses FSF GDB.
\o In the \gui Debugger field, specify the path to FSF GDB
(\c $HOME/gdb72/bin/fsfgdb, but with an explicit value for
\c $HOME).
\o To use the debugger, add the target in the \gui {Build Settings}
\o To use the debugger, add the kit in the \gui {Build Settings}
of the project.
\endlist

11
doc/src/debugger/creator-debugger.qdoc
View File

@@ -252,9 +252,9 @@
While this setup might look daunting, it is mostly invisible to
the user of \QC. To start debugging on a remote target with the
necessary helper processes running, select the target in
\gui{Projects > Build Settings}
or in the \gui{Debug > Start Debugging} menu.
necessary helper processes running, select the corresponding
\l{glossary-buildandrun-kit}{kit} in
\gui{Projects > Build & Run} or in the \gui{Debug > Start Debugging} menu.
Special use cases, such as attaching to a running process on the
target, might still require manual setup.
@@ -693,8 +693,7 @@
which may contain both release and debug versions of the library. When you run
applications on the Mac OS desktop, the release version of Frameworks is used
by default. To step into Frameworks, select the \gui {Use debug versions of
Frameworks} option in the project run settings for \gui Desktop and
\gui {\QS} targets.
Frameworks} option in the project run settings.
\section2 Viewing Threads
@@ -792,7 +791,7 @@
To give the user simple access also to these items, \QC employs
so-called Debugging Helpers. Debugging Helpers come in two varieties,
compiled, and Python based, depending on the selected
\l{glossary-development-target}{target}.
\l{glossary-buildandrun-kit}{kit}.
By default, Debugging Helpers are automatically and transparently used.
To disable them, select \gui Tools > \gui Options > \gui Debugger >

2
doc/src/debugger/qtquick-debugging.qdoc
View File

@@ -89,7 +89,7 @@
\o To debug applications on devices, check that Qt 4.7.4, or later,
libraries are installed on the device and
\l{Running on Multiple Targets}{select the device as the target}
\l{Running on Multiple Targets}{select the corresponding kit for the device}
before you start debugging.
\endlist