[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Wrong order of preprocessor and compiler flags
From: |
Zack Weinberg |
Subject: |
Re: Wrong order of preprocessor and compiler flags |
Date: |
Thu, 24 Mar 2022 12:08:39 -0400 |
User-agent: |
Cyrus-JMAP/3.5.0-alpha0-4911-g925b585eab-fm-20220323.003-g925b585e |
On Thu, Mar 24, 2022, at 11:13 AM, Nick Bowler wrote:
> On 2022-03-23, Zack Weinberg <zack@owlfolio.org> wrote:
>> ... before we change
>> anything, we need to check what the rules *built into GNU and BSD
>> Make* do with CFLAGS and CPPFLAGS (and also CXXFLAGS, OBJCFLAGS, etc)
>> because those are much much harder to get changed than anything in
>> Automake or Autoconf, so we should aim to harmonize everything with
>> them.
>
> Practically all make implementations use the $(CFLAGS) $(CPPFLAGS)
> ordering in their builtin .c.o inference rules.
>
> However, GNU coding standards state that CFLAGS should be the last
> item on compilation commands, so it would appear that this is a case
> where traditional "make" behaviour contrasts with GNU standards (which
> Automake is following).
Huh. Is there a rationale given in the coding standard? If not, do you have
any idea who might remember the rationale?
zw
Re: Wrong order of preprocessor and compiler flags, Evgeny Grin, 2022/03/24