Lines Matching +full:debian +full:- +full:build +full:- +full:testing

13 The tools used for code coverage are known to work on Ubuntu and Debian. They
14 should work correctly on newer versions of Ubuntu, Debian and related Linux
18 `llvm-cov` to be present. This is no longer true, so if you have no other need
20 Clang build tools directory by the script.
29 Before generating code coverage information, you will need to have a build
40 If you already have a build directory, you can append the coverage flag to the
55 `testing/tools/coverage/coverage_report.py` script. This script will download
56 the Clang coverage tools if needed, build any binaries that it needs, perform
62 currently at the root of your PDFium checkout, the build directory to use is
66 testing/tools/coverage/coverage_report.py
70 you will need to pass in `--source-directory` with the appropriate directory. If
71 you are using a different build directory, then `--build-directory` will need to
73 you will need to pass in `--output-directory`.
78 testing/tools/coverage/coverage_report.py \
79     --source-directory ~/pdfium/pdfium \
80     --build-directory ~/pdfium/pdfium/out/Debug_with_Coverage \
81     --output-directory ~/Documents/PDFium_coverage
86 tests can be found by running the script with `--help`.
91 testing/tools/coverage/coverage_report.py pdfium_unittests pdfium_embeddertests
100 There are additional developer debugging flags available, `--dry-run` and
101 `--verbose`. `--dry-run` will output a trace of commands that would have been
102 run, but doesn't actually execute them. `--verbose` turns on outputting