NFD

Would this help: http://stackoverflow.com/questions/11936226/how-to-prevent-waf-from-renaming-object-files

To have code coverage checking, the code has to be compiled to generate some temporary files (for gcov, two kinds of file, ".gcno" and ".gcda", are generated) that indicates the code structure and the count of execution of each line.

I followed the instruction from online to run gcovr. However, gcovr shows that everything has a code coverage of 0% (It is not detecting anything even after I run unit tests).

For some reason our code is not generating any ".gcda" files after running unit test when compile with these flags: "-fprofile-arcs -ftest-coverage -fPIC".

Expected behavior:

I have also written a very simple c++ program just like the examples at http://gcovr.com/guide.html. The behavior is as follows:

1. When I compile with "-fprofile-arcs -ftest-coverage -fPIC", I can see ".gcno" file that is created but no ".gcda" file there.

2. Then I run the executable produced by g++. After that, the ".gcda" files are created.

3. After that, I run "gcovr -r .", and I am able to see the output that makes sense.

Please submit your change of wscript and other files to Gerrit, so that we can see what's the problem.

Yi and I was playing around yesterday and I suspect that clang is not working well with gcc-style code coverage. Have you tried it on Linux?

Yes I created a all new VM on maestro. Things from my last post are all from that VM (I tested ndn-cpp-dev and did the experiment of simple code there).

To submit wscript, do I commit wscript only and push to origin HEAD:refs/for/new-dev ?

Before submitting, do the following change

Add in the options section:

opt.add_option('--with-coverage',action='store_true',default=False,dest='with_coverage',
               help='''Set compiler flags for gcc to enable code coverage information''')

In configure section:

if conf.options.with_coverage:
    conf.check_cxx(cxxflags=['-fprofile-arcs', '-ftest-coverage', '-fPIC'], uselib_store='GCOV', mandatory=True)

And in the build section, add GCOV to "use" parameter for necessary items.

For ndn-cpp-dev we are using master branch, so submit there. You can also, like Hila, add the topic. I believe it is done like git push origin HEAD:refs/for/master/some_topic_here

I'm not sure how to 'in the build section, add GCOV to "use" parameter for necessary items.'

Do I need to discard the changes I made to 'conf.add_supported_cxxflags' since we are now using the option thing?

Assuming you're modifying ndn-cpp-dev's wscript:

libndn_cpp = bld (
    features=['cxx', 'cxxstlib'], # 'cxxshlib',
    # vnum = "0.3.0",
    target="ndn-cpp-dev",
    name = "ndn-cpp-dev",
    source = bld.path.ant_glob('src/**/*.cpp',
                               excl = ['src/**/*-osx.cpp', 'src/**/*-sqlite3.cpp']),
    use = 'BOOST OPENSSL LOG4CXX CRYPTOPP SQLITE3 RT PIC PTHREAD GCOV',
    includes = ". src",
    export_includes = "src",
    install_path = '${LIBDIR}',
    )

And yes, discard add_supported_flags, since it has slightly different purpose (will just add flags if supported and not going to force/fail when flags are not working, which is desirable in this case).

What's the intended outcome of this task?

If CodeCoverage document is sufficient, this task should be Closed.

If Jenkins installation is desired, work should continue.