[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: common c(xx)flags for compilation?
From: |
Karl Berry |
Subject: |
Re: common c(xx)flags for compilation? |
Date: |
Mon, 16 May 2016 21:11:56 GMT |
Another possible name would be COMPILERFLAGS
I like it.
If "people" (Brandon?) think it's worthwhile, I could make up the patch
to propose to rms.
However, I realized that in practice it would conceivably be more
useful to have the generic options after the compiler-specific options,
even though that is not logical.
The reason is that one of the principal reasons I bothered to write this
was because it would be nice to be able to say make SOMEVAR=-g and
get just debugging, no optimization, for all compilers. But if
COMPILERFLAGS comes before CFLAGS, that won't be the result. Whereas if
the new var comes after, then SOMEVAR="-g -OO" will do it.
The strictly logical approach would be to put the default "-g -O2"
(being generic options) into the new variable instead of the traditional
CFLAGS, CXXFLAGS, etc. But I think that is too big a break with
tradition and will surely mess up plenty of existing build processes.
So I wouldn't want to go there.
So maybe there is no hope and we are stuck with the status quo. Sigh. -k