Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for custom code coverage analysis tools #43

Open
Blumentopf99 opened this issue Mar 29, 2023 · 0 comments
Open

Support for custom code coverage analysis tools #43

Blumentopf99 opened this issue Mar 29, 2023 · 0 comments

Comments

@Blumentopf99
Copy link

I have another request.
Besides lcov we're also using gcovr for some of our projects and we have our own script that generates the coverage report. For those projects I'm still using your code-coverage.cmake module as basis w.r.t. the compiler settings and I just create a custom cmake tarket to produce the coverage report analog to ccov-capture-${target_code_coverage_COVERAGE_TARGET_NAME}.
Everything works fine, but I'd like to suppress the implicitly created ccov-* targets to keep the list of available targets clean. Can you think of a simple way to support that? Perhaps by offering a cmake option like the following?

option(
  DISABLE_COVERAGE_TOOLS
  "If ON then no targets are created for the built-in supported coverage tools."
  OFF)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant