Date: Tue, 28 Feb 2012 16:22:24 -0800 From: Ade Lovett <ade@FreeBSD.org> To: Chuck Burns <break19@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: setting CC/CXX/CPP unconditionally in src.conf Message-ID: <4F4D6FC0.4070501@FreeBSD.org> In-Reply-To: <4F4D6C7D.3030109@gmail.com> References: <20120226213703.GA33988@freebsd.org> <4F4D34C8.9080507@FreeBSD.org> <20120228221149.GA95661@freebsd.org> <4F4D5B63.6020306@FreeBSD.org> <4F4D6C7D.3030109@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2/28/2012 16:08, Chuck Burns wrote:
> On 2/28/2012 4:55 PM, Ade Lovett wrote:
>> On 2/28/2012 14:11, Alexander Best wrote:
>>> any chance we can have a CFLAGS.gcc and CFLAGS.clang in the future?
>>> that would
>>> make certain things a lot easier. dealing with gcc specific options,
>>> such as
>>> -mpreferred-stack-boundary=2 would simply work by setting
>>> CFLAGS.gcc=-mpreferred-stack-boundary=2 e.g.
>>
>> You already can:
>>
>> CFLAGS.cc= cc_cflags_here
>> CFLAGS.clang= clang_cflags_here
>>
>> CFLAGS+= generic_cflags_here
>> CFLAGS+= ${CFLAGS.${CC}}
>>
>>
>> -aDe
>
> I think was asking for adding a third...
> .cc for base gcc
> .clang for .. clang......
> and .gcc for ports gcc4x
> ..
>
> At least, thats how I read it, I could be wrong, it's happened before.
CFLAGS.gcc46= <foo>
CFLAGS.gcc47= <bar>
...
it's entirely extensible.
-aDe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F4D6FC0.4070501>