[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Radiusplugin-devel] Drop unstandard colored build log in favor of s
From: |
Ralf Lübben |
Subject: |
Re: [Radiusplugin-devel] Drop unstandard colored build log in favor of standard quiet or V=1 build |
Date: |
Wed, 29 Aug 2012 12:33 +0200 |
User-agent: |
KMail/4.8.4 (Linux/3.2.0-29-generic-pae; KDE/4.8.4; i686; ; ) |
Added to CVS.
Am Samstag, 4. August 2012, 12:12:19 schrieb address@hidden:
> Current Makefile (2.1 and CVS) is a bit exotic and have some drawback.
>
> The most important for me is that there is no way to set the optimization
> level. This matter when trying to harden the build as FORTIFY require -O2
> or more (-Os or -O3).
>
> Makefile should use CXXFLAGS instead of CFLAGS for g++
> If using g++, CXX should be used instead of CC
>
> Don't reset LDFLAGS in Makefile in case one put a smart value there.
> If one put stupid value in LDFLAGS, he win the right to be burn.
>
> Drop the color code that result in ugly [<x>m in text log
> Instead use the standard V=1 for verbose compilation, not using V=1
> resulting in non verbose compilation. V=1 allow to check what values are
> really used in ...FLAGS
>
> Gilles