%% Ossama Othman <[EMAIL PROTECTED]> writes:
oo> I've had complaints from users about the fact that my configure script
oo> adds "-g -O2" to CXXFLAGS by default since they want to compile an
oo> optimized version of the library without debugging symbols. I know
oo> that gcc/g++ can generate debugging symbols for optimized code, but
oo> that's not the issue. The issue here is that the user doesn't appear
oo> to have a choice about the "-g -O2" flags. Is this correct? If so,
oo> why does autoconf add these? Shouldn't it be up to the package
oo> maintainer to decide whether these flags get added to the compiler
oo> flags?
It's not correct. If they read the INSTALL file (you do ship the
autoconf INSTALL file with your package, right?) they'll see they can do
either of these things to override the default value:
$ CXXFLAGS=-g ./configure ...
$ make
(that's sh/ksh/bash/zsh syntax; if you're using csh/tcsh you need to add
an "env " to the beginning of the configure line) or
$ ./configure ...
$ make CXXFLAGS=-g
(the latter assumes you're makefiles are properly constructed so that
they don't add important options to CXXFLAGS and leave them to the user
for modification, as the GNU coding standards require).
HTH! :)
--
-------------------------------------------------------------------------------
Paul D. Smith <[EMAIL PROTECTED]> Network Management Development
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
These are my opinions---Nortel Networks takes no responsibility for them.
