Robert Edmonds e72e7e7e81 add code coverage option to the build system ...

configure now has a "--enable-code-coverage" option, and if the
lcov/gcov tools are available a code coverage report can be built with
"make check-code-coverage".

this is mostly based on the AX_CODE_COVERAGE / GNOME_CODE_COVERAGE
macro:

    http://savannah.gnu.org/patch/?8451

but i also looked at knot-dns's code coverage implementation:

    https://github.com/CZNIC-Labs/knot/blob/master/m4/code-coverage.m4

and kevin lyda's pull request:

    https://github.com/protobuf-c/protobuf-c/pull/131/files

2014-06-02 17:56:41 -04:00

..

.gitignore

new build system

2013-11-16 18:08:40 -05:00

ax_prog_doxygen.m4

Autoconf configuration for doxygen.

2014-02-16 21:45:02 +00:00

code_coverage.m4

add code coverage option to the build system

2014-06-02 17:56:41 -04:00

ld-version-script.m4

version the libprotobuf-c symbols on compatible linkers (Issue #116)

2014-03-27 15:22:55 -04:00

pkg.m4

new build system

2013-11-16 18:08:40 -05:00

valgrind-tests.m4

.travis.yml: add a travis build entry to run tests under valgrind

2014-01-14 00:20:05 -08:00