forked from qt-creator/qt-creator
Device type + tool chain + other settings -> Kit
We called that "Target" before Change-Id: Ie0d673c643947c26ac2706907f6250fc1739388a Reviewed-by: Leena Miettinen <riitta-leena.miettinen@nokia.com>
This commit is contained in:
@@ -37,8 +37,8 @@
|
||||
to use them from \QC.
|
||||
|
||||
To run the Valgrind tools on a remote host over SSH, select \gui {Analyze
|
||||
> Valgrind Analyze Memory (Remote)} or \gui {Valgrind Function Profile
|
||||
(Remote)}.
|
||||
> Valgrind Analyze Memory (External)} or \gui {Valgrind Function Profile
|
||||
(External)}.
|
||||
|
||||
To stop the currently running analyzer, select \gui {Analyze
|
||||
> Stop}.
|
||||
|
||||
@@ -252,15 +252,13 @@
|
||||
|
||||
\list 1
|
||||
|
||||
\o Select \gui {Analyze > Valgrind Analyze Memory (Remote)} or
|
||||
\gui {Valgrind Function Profile (Remote)}.
|
||||
\o Select \gui {Analyze > Valgrind Analyze Memory (External)} or
|
||||
\gui {Valgrind Function Profile (External)}.
|
||||
|
||||
\image qtcreator-valgrind-remote-settings.png "Start Debugger dialog"
|
||||
\image qtcreator-valgrind-remote-settings.png "Start Analyzer dialog"
|
||||
|
||||
\o In the \gui Remote group, specify the connection to the remote host.
|
||||
|
||||
\o In the \gui Target group, specify the application to run and analyze
|
||||
on the remote host.
|
||||
\o Specify the application to run and analyze, and the \l{glossary-buildandrun-kit}{kit}
|
||||
to use.
|
||||
|
||||
\endlist
|
||||
|
||||
|
||||
@@ -87,7 +87,7 @@
|
||||
\section1 Attaching to Running Qt Quick Applications
|
||||
|
||||
To profile Qt Quick applications that are not launched by \QC, select
|
||||
\gui {Analyze > QML Profiler (Remote)}. You must enable QML debugging for
|
||||
\gui {Analyze > QML Profiler (External)}. You must enable QML debugging for
|
||||
the application in the project build settings. For more information, see
|
||||
\l{Setting Up QML Debugging}.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user