search

adentinger / CMakeBestPractices

A reference CMake configuration for fairly scalable open-/closed-source C/C++ projects
MIT License
2 stars 0 forks source link

Setup code coverage report #68

Open adentinger opened 1 year ago

adentinger commented 1 year ago

Never tried this sort of thing before, so have to reasearch exactly what they do, why they're useful, and how/if to fit them in the environment.

adentinger commented 8 months ago

After some reseach (gcov vs lcov vs bcov vs kcov), I'll be adding support for gcov. kcov seems interesting for interactive use (directly creates the report index.html file), but gcov seems better-known and is supported by CMake.

I'd thinkg of coverage support as implemented in the CI as a new CI job and not as a part of the analysis job, since coverage requires a special build (requires debug symbols, and special build flags).

Additionally, since CMake's Coverage wiki page specifies a bunch of specific build flags for coverage to work, we'll have to wait until #64 is done to implement support for it.