I recently started using lcov to visualize my code coverage. It\'s a great tool.
One thing I\'m noticing is that it generates code coverage reports for all the file
A possible approach is to constrain which files are compiled with the coverage flags (-fprofile-arcs -ftest-coverage). If you don't want to engineer your make file system to be selective about which files are built with test instrumentation, the following trick might work for you:
This should result in only the targeted areas emitting gcov artifacts, which are blindly consumed by the lcov scripts.