Can gcc/gcov be made to output coverage stats to a location other than the source folder?

gcc gcov code-coverage
kdt picture kdt · Sep 17, 2009 · Viewed 8.1k times · Source

When using gcc with -fprofile-arcs and -ftest-coverage, when the resulting executable terminates, it tries to create .gcda output files in the same location as the .o files used to compile the executable. This is inconvenient when I'm running on a different machine than the one I built on -- is there any way to change this behaviour?

Answer

F'x picture F'x · Sep 19, 2009

You can use the environment variable GCOV_PREFIX. It's mentionned in the doc under a "cross-profiling" section, which itself is referred to in the documentation for -fprofile-arcs.

Related questions

gcov on larger projects (static libraries, ...)

I'm working on larger project which has the following directory layout: Source MyA aa.cpp ab.cpp ac.cpp MyB ba.cpp bb.cpp bc.cpp MyTest testaa.cpp testab.cpp testac.cpp testba.cpp testbb.cpp testbc.cpp main.…

Read More
gcov: producing .gcda output from shared library?

Is it possible to produce gcov data files (.gcda files) by running an executable linked to a shared library built with the --coverage option? Basically, I have the main library consisting of multiple c++ files compiled into one shared library …

Read More
GCOV: What is the difference between --coverage and --ftest-coverage when building with GCC?

Trying to get code coverage up and running, and I'm just reading documentation first. I found a few articles that mention building with the --coverage flag, while others mention the --ftest-coverage. Both descriptions seem to say they do the same …

Read More