grim/gplate

pulled the code coverage stuff out to it's own configure argument (--enable-code-coverage). Lumping it in with --enable-debug was stupid anyways :)

2009-06-23, Gary Kramlich
1a82b5b1973c
Parents 3bbcdc9c559a
Children 8dd8e90f1d0b
pulled the code coverage stuff out to it's own configure argument (--enable-code-coverage). Lumping it in with --enable-debug was stupid anyways :)
1 files changed, 8 insertions(+), 1 deletions(-)
  • +8 -1
    configure.ac
    • --- a/configure.ac Mon Jun 22 16:45:07 2009 -0500
    +++ b/configure.ac Tue Jun 23 23:09:16 2009 -0500
    @@ -137,10 +137,17 @@
    ,,enable_debug=no)
    if test x"$enable_debug" = x"yes" ; then
    - CFLAGS="$CFLAGS -O0 -fprofile-arcs -ftest-coverage"
    + CFLAGS="$CFLAGS -O0"
    AC_DEFINE(DEBUG, 1, [Define if debugging is enabled.])
    fi
    +AC_ARG_ENABLE(code_coverage,
    + AC_HELP_STRING([--enable-code-coverage],[compile with code coverage support])
    + ,,enable_code_coverage=no)
    +if test x"$enable_code_coverage" = x"yes" ; then
    + CFLAGS="$CFLAGS -fprofile-arcs -ftest-coverage -fPIC"
    +fi
    +
    if test x"$GCC" = x"yes"; then
    CFLAGS="$CFLAGS -Wall -g3"
    fi