Doc: specifying analyzer settings at project level

Change-Id: Ic0d68dbaf3a1b57a56b3e2cb2670399460df8589
Reviewed-by: hjk <qthjk@ovi.com>

5 files changed, 46 insertions, 0 deletions

diff --git a/doc/images/qtcreator-analyze-menu.png b/doc/images/qtcreator-analyze-menu.png
index 221dae9e9d..04b289dcf7 100644
--- a/doc/images/qtcreator-analyze-menu.png
+++ b/doc/images/qtcreator-analyze-menu.png
diff --git a/doc/images/qtcreator-analyzer-settings.png b/doc/images/qtcreator-analyzer-settings.png
new file mode 100644
index 0000000000..ee308a9ca5
--- /dev/null
+++ b/doc/images/qtcreator-analyzer-settings.png
diff --git a/doc/src/analyze/creator-valgrind.qdoc b/doc/src/analyze/creator-valgrind.qdoc
index 43a00bdfa9..a620397e51 100644
--- a/doc/src/analyze/creator-valgrind.qdoc
+++ b/doc/src/analyze/creator-valgrind.qdoc
@@ -82,6 +82,10 @@
 
     \section1 Selecting Options for Memory Analysis
 
+    You can specify analyzer settings either globally for all projects or
+    separately for each project in the \l{Specifying Run Settings}{run settings}
+    of the project.
+
     Stack traces can get quite large and confusing, and therefore, reading them
     from the bottom up can help. If the stack trace is not big enough or it is
     too big, select \gui {Tools > Options > Analyzer}.
@@ -168,6 +172,10 @@
 
     \section1 Selecting Profiling Options
 
+    You can specify analyzer settings either globally for all projects or
+    separately for each project in the \l{Specifying Run Settings}{run settings}
+    of the project.
+
     To specify settings for Valgrind, select \gui {Tools > Options >
     Analyzer}. The \gui {Profiling Options} group contains Callgrind options.
 
diff --git a/doc/src/projects/creator-projects-settings-run-analyze.qdocinc b/doc/src/projects/creator-projects-settings-run-analyze.qdocinc
new file mode 100644
index 0000000000..432baf0ae4
--- /dev/null
+++ b/doc/src/projects/creator-projects-settings-run-analyze.qdocinc
@@ -0,0 +1,37 @@
+    \section2 Specifying Analyzer Settings
+
+    \QC integrates \l{Analyzing Code}{Valgrind code analysis tools} for
+    detecting memory leaks and profiling function execution. You can configure
+    the tools according to your needs.
+
+    You can specify analyzer settings for the desktop and Qt Simulator targets.
+    You can specify them either globally for all projects or separately for each
+    project.
+
+    To specify analyzer settings for the current project:
+
+    \list 1
+
+        \o  In the \gui {Analyzer Settings} section, select \gui Custom.
+
+        \o  Specify analyzer settings for the project.
+
+            \image qtcreator-analyzer-settings.png "Analyzer Settings"
+
+    \endlist
+
+    For more information about the settings, see:
+
+    \list
+
+        \o  \l{Selecting Options for Memory Analysis}
+
+        \o  \l{Selecting Profiling Options}
+
+    \endlist
+
+    Click \gui {Restore Global} to revert to the global settings.
+
+    To specify global analyzer settings, select \gui {Tools > Options >
+    Analyzer}.
+
diff --git a/doc/src/projects/creator-projects-settings-run.qdoc b/doc/src/projects/creator-projects-settings-run.qdoc
index 5eb801724e..3636b53183 100644
--- a/doc/src/projects/creator-projects-settings-run.qdoc
+++ b/doc/src/projects/creator-projects-settings-run.qdoc
@@ -50,6 +50,7 @@
 
     \if defined(qcmanual)
     \input projects/creator-projects-settings-run-desktop.qdocinc
+    \input projects/creator-projects-settings-run-analyze.qdocinc
     \input symbian/creator-projects-settings-run-symbian.qdocinc
     \input linux-mobile/creator-projects-settings-run-madde.qdocinc
     \input linux-mobile/creator-projects-settings-run-generic-linux.qdocinc