Revision history [back]

I'm not directly familiar with CMake's Coverage build type, but if it creates binaries instrumented with gcov (fi) then wouldn't the profiling data be generated upon executing the binary, and in the cwd?

I'm not directly familiar with CMake's Coverage build type, but if it creates binaries instrumented with gcov (fi) then wouldn't the profiling data be generated upon executing the binary, and in the cwd?

I'm not directly familiar with CMake's CMake's rosbuild's Coverage build type, but if it creates binaries instrumented with gcov (fi) then wouldn't the profiling data be generated upon executing the binary, and in the cwd?

Edit: also, is the Coverage build type still supported with catkin? I can only find references to it in rosbuild CMakeLists.txt.

I'm not directly familiar with CMake's rosbuild's the Coverage build type, but if it creates binaries instrumented with gcov (fi) then wouldn't the profiling data be generated upon executing the binary, and in the cwd?

Edit: also, is the Coverage build type still supported with catkin? I can only find references to it in rosbuild CMakeLists.txt.

I'm not directly familiar with the Coverage build type, but if it creates binaries instrumented with gcov (fi) then wouldn't the profiling data be generated upon executing the binary, and in the cwd? No.

Edit: also, is the Coverage build type still supported with catkin? I can only find references to it in rosbuild CMakeLists.txt.

Edit2: according to this stack overflow answer, the coverage information ends up in the directory where the object files are, so for CMake / catkin that would probably be in the build space of your workspace.