On Wed, 6 Aug 2008, Eric Blake - [EMAIL PROTECTED] wrote:
According to Bruno Haible on 8/6/2008 4:41 PM:
| But autoconf still hardwires this logic in _AC_PROG_CC_G:
|
| ---------------------------------------------
| elif test $ac_cv_prog_cc_g = yes; then
| if test "$GCC" = yes; then
| CFLAGS="-g -O2"
|
| Could this be made customizable somehow? Either through a variable that the
| developer could set in his configure.ac before the invocation of
AC_PROG_CC,
| or through a macro which he could redefine in his configure.ac?
Hmm. This is an interesting request, and seems doable.
I'll put in a modified request. A few projects break these options out
into things like
--enable-debug
--enable-warnings
--disable-optimization or --with-optimization=N
etc.
They then try to interpret the compiler found by autoconf to make
decisions like "GCC uses -g and -Wall"... These are common end-user
flags; it would be nice if autoconf provided a standard framework to
detect and use them.
Thanks,
Daniel
