aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/markdown/Feature-autodetection.md23
-rw-r--r--docs/markdown/Unit-tests.md2
2 files changed, 20 insertions, 5 deletions
diff --git a/docs/markdown/Feature-autodetection.md b/docs/markdown/Feature-autodetection.md
index f865174..f50309e 100644
--- a/docs/markdown/Feature-autodetection.md
+++ b/docs/markdown/Feature-autodetection.md
@@ -4,16 +4,31 @@ short-description: Auto-detection of features like ccache and code coverage
# Feature autodetection
-Meson is designed for high productivity. It tries to do as many things automatically as it possibly can.
+Meson is designed for high productivity. It tries to do as many things
+automatically as it possibly can.
CCache
--
-[CCache](https://ccache.samba.org/) is a cache system designed to make compiling faster. When you run Meson for the first time for a given project, it checks if CCache is installed. If it is, Meson will use it automatically.
+[CCache](https://ccache.samba.org/) is a cache system designed to make
+compiling faster. When you run Meson for the first time for a given
+project, it checks if CCache is installed. If it is, Meson will use it
+automatically.
-If you do not wish to use CCache for some reason, just specify your compiler with environment variables `CC` and/or `CXX` when first running Meson (remember that once specified the compiler can not be changed). Meson will then use the specified compiler without CCache.
+If you do not wish to use CCache for some reason, just specify your
+compiler with environment variables `CC` and/or `CXX` when first
+running Meson (remember that once specified the compiler can not be
+changed). Meson will then use the specified compiler without CCache.
Coverage
--
-When doing a code coverage build, Meson will check the existence of binaries `gcovr`, `lcov` and `genhtml`. If the first one is found, it will create targets called *coverage-text* and *coverage-xml*. If the latter two or a new enough `gcovr` is found, it generates the target *coverage-html*. You can then generate coverage reports just by calling e.g. `ninja coverage-xml`.
+When doing a code coverage build, Meson will check for existence of
+the binaries `gcovr`, `lcov` and `genhtml`. If version 3.3 or higher
+of the first is found, targets called *coverage-text*, *coverage-xml*
+and *coverage-html* are generated. Alternatively, if the latter two
+are found, only the target *coverage-html* is generated. Coverage
+reports can then be produced simply by calling e.g. `ninja
+coverage-xml`. As a convenience, a high-level *coverage* target is
+also generated which will produce all 3 coverage report types, if
+possible.
diff --git a/docs/markdown/Unit-tests.md b/docs/markdown/Unit-tests.md
index 9e61739..694c190 100644
--- a/docs/markdown/Unit-tests.md
+++ b/docs/markdown/Unit-tests.md
@@ -30,7 +30,7 @@ Note how you need to specify multiple values as an array.
Coverage
--
-If you enable coverage measurements by giving Meson the command line flag `-Db_coverage=true`, you can generate coverage reports. Meson will autodetect what coverage generator tools you have installed and will generate the corresponding targets. These targets are `coverage-xml` and `coverage-text` which are both provided by [Gcovr](http://gcovr.com) and `coverage-html`, which requires [Lcov](https://ltp.sourceforge.io/coverage/lcov.php) and [GenHTML](https://linux.die.net/man/1/genhtml) or [Gcovr](http://gcovr.com) with html support.
+If you enable coverage measurements by giving Meson the command line flag `-Db_coverage=true`, you can generate coverage reports. Meson will autodetect what coverage generator tools you have installed and will generate the corresponding targets. These targets are `coverage-xml` and `coverage-text` which are both provided by [Gcovr](http://gcovr.com) (version 3.3 or higher) and `coverage-html`, which requires [Lcov](https://ltp.sourceforge.io/coverage/lcov.php) and [GenHTML](https://linux.die.net/man/1/genhtml) or [Gcovr](http://gcovr.com). As a convenience, a high-level `coverage` target is also generated which will produce all 3 coverage report types, if possible.
The output of these commands is written to the log directory `meson-logs` in your build directory.