autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to enable/disable my debug code?


From: narke
Subject: Re: How to enable/disable my debug code?
Date: Wed, 27 Jul 2011 20:22:59 +0800

Hi, Gary

On 27 July 2011 14:36, Gary V. Vaughan <address@hidden> wrote:
> On 27 Jul 2011, at 12:56, narke wrote:
>> With a same set of autoconf/automake files, how to I distribute my
>> program that allows user to build it with or without debug code
>> enabled?  In my code, there are something like below:
>>
>> #if (__MY_DEBUG__)
>> ...
>> #endif
>>
>> Thanks in advance.
>
>
> For debug builds:
>
>  ./configure CFLAGS='-g' CPPFLAGS=-D__MY_DEBUG__
>

For this approach, will it overwrite my already defined flags or just
append values to them?  It usual that my CPPFLAGS had already set as
something like "-I/my/include" in a Makefile.am

> For regular builds:
>
>  ./configure
>
> If you use assert.h, you can also speed things up a bit more by turning
> off the assertions with:
>
>  ./configure CPPFLAGS=-DNDEBUG
>
> Of course you can write (or find and copy) some Autoconf M4 code to
> do some or all of the above automatically depending on the presence
> of configure options like:
>
>  ./configure --enable-debug
>
> Googling for 'AC_ARG_ENABLE debug' turns up many examples such as:
>
>  AC_ARG_ENABLE([debug],
>    [  --enable-debug           build with additional debugging code],
>    [CFLAGS='-g';AC_DEFINE([__MY_DEBUG__])])
>

I prefer this approach, thank for showing the example!

> HTH,
> --
> Gary V. Vaughan (gary AT gnu DOT org)
>



-- 
Life is the only flaw in an otherwise perfect nonexistence
    -- Schopenhauer

narke
public key at http://subkeys.pgp.net:11371 (address@hidden)



reply via email to

[Prev in Thread] Current Thread [Next in Thread]