coverage version mismatch: version '402*', prefer 'A83*'

[jayvdb]

In https://github.com/jayvdb/libsbp/runs/3201507973?check_suite_focus=true, run with -DCMAKE_C/CXX_COMPILER=clang/clang++, all files produce the following:

Running phase [post]: lcov --compat-libtool --capture --directory . | sed s@^SF:/github/workspace/c/@SF:@ > lcov.info && lcov --list lcov.info
  + lcov --compat-libtool --capture --directory . | sed s@^SF:/github/workspace/c/@SF:@ > lcov.info && lcov --list lcov.info
  Capturing coverage data from .
  Found gcov version: 8.3.0
  Scanning . for .gcda files ...
  Found 182 data files in .
  Processing src/CMakeFiles/sbp.dir/edc.c.gcda
  /github/workspace/c/src/CMakeFiles/sbp.dir/edc.c.gcno:version '402*', prefer 'A83*'
  /github/workspace/c/src/CMakeFiles/sbp.dir/edc.c.gcno:no functions found
  /github/workspace/c/src/CMakeFiles/sbp.dir/edc.c.gcda:version '402*', prefer version 'A83*'
  geninfo: WARNING: gcov did not create any files for /github/workspace/c/src/CMakeFiles/sbp.dir/edc.c.gcda!
...

[lpenz]

From gcov-out-of-memory-mismatched-version it seems that lcov is highly coupled to the compiler, which would be gcc in this Debian release.
There's probably something equivalent for clang, maybe in llvm. I don't think the test coverage is going to be much different, though.

[jayvdb]

When I enable CODE_COVERAGE=ON, the magic in https://github.com/swift-nav/cmake/blob/master/CodeCoverage.cmake fixes the problem. Possibly something in there is able to be adopted?

[lpenz]

Interesting, it looks like clang has a different set of arguments for coverage.
How about a coverage-clang preset? I'm afraid just incrementing the arguments could make gcc unhappy.

[jayvdb]

How about a coverage-clang preset?

That would work for me.