diff options
| author | Robert Griebl <robert.griebl@qt.io> | 2021-06-28 04:26:28 +0200 |
|---|---|---|
| committer | Robert Griebl <robert.griebl@qt.io> | 2021-06-28 18:20:07 +0200 |
| commit | cd088bb1b7c305e3455bc19a416d29c1cffc3b9e (patch) | |
| tree | 66e9fa254796d190eb9c60aa20228f193a44222a /doc | |
| parent | 37d87aa343f0367ab9e8456296f423031c21bb34 (diff) | |
| download | qtapplicationmanager-cd088bb1b7c305e3455bc19a416d29c1cffc3b9e.tar.gz | |
Add back a check_coverage target
Activate it by running cmake with -DAM_COVERAGE=ON
Change-Id: Ifea2f4813fa9716eccd5fb01639b1868976f86aa
Reviewed-by: Dominik Holland <dominik.holland@qt.io>
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/installation.qdoc | 11 |
1 files changed, 5 insertions, 6 deletions
diff --git a/doc/installation.qdoc b/doc/installation.qdoc index d9f51d08..99d2cc12 100644 --- a/doc/installation.qdoc +++ b/doc/installation.qdoc @@ -217,23 +217,22 @@ There are three different ways to specify a hardware ID: All executables, including the unit tests, can be found in the build folder's \c bin directory, after compiling. -\omit + \section1 Generate Code-Coverage Data -Instead of doing a normal build, you can also create a coverage build by running \c{make coverage}. -Since every compile step needs to be instrumented with special compiler flags, make sure to run -\c{make clean} before \c{make coverage}. +Instead of doing a normal build, you can also create a coverage build by running +\c{cmake -DAM_COVERAGE=ON}. Since every compile step needs to be instrumented with special compiler +flags, make sure to create a new build directory, or at least clean an existing one. Using a build like this enables you to generate HTML coverage reports with the following command in the build directory: \badcode -make check-coverage +cmake --build . --target check_coverage \endcode The command line output provides you the URL to the generated report. -\endomit \section1 System Setup |