--enable-debug=full is a VERY bad option??? (was: Re: gcc flags for developers)

[Ingo Klöcker]

On Friday 09 December 2005 12:10, Dirk Mueller wrote:
> On Thursday 08 December 2005 02:02, Michael Pyne wrote:
> > I'd be interested in hearing (and fixing) these "horrifying hacks".
> >
> > Especially since there is no code in kdesvn-build to alter the
> > CXXFLAGS (they are read from the user's .kdesvn-buildrc).
>
> Well, did you read the sample kdesvn-buildrc in the light of the
> recent discussion?
>
> it contains lines such as:
>
> configure-flags --enable-debug=full
> cxxflags -g -pipe -march=i686
>
> Thats wrong on so many levels:
>
> - first of all it shouldn't be cxxflags. we have C code as well
>
> - hardcoding -march is wrong
>
> - setting -g after --enable-debug=full is plain stupid, because it
> overwrites what --enable-debug=full already did.
>
> - Also, full is a VERY bad option, as it disables important WARNINGS.

Am I missing something? I thought --enable-debug=full is what every 
developer should be using? If this isn't the case then what should I be 
using?

Regards,
Ingo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20051209/e46ebb4a/attachment.sig>