On Fri, 18 May 2001 12:44:31 +0200 (CEST),
Kai Germaschewski <[EMAIL PROTECTED]> wrote:
>Okay, I think you're right, the logical separation is not worth the
>additional complexity. But why not leave the CPP variable at least?
On second thoughts I will keep CPP, it is a useful indication that the
On Fri, 18 May 2001, Keith Owens wrote:
> That is precisely my problem, it is not done cleanly at the moment.
> We currently have, in roughly this order
>
> global cppflags in top level makefile
> include list from top level makefile
> module/kernel flags from top level makefile
> global
On Fri, 18 May 2001 09:41:51 +0200 (CEST),
Kai Germaschewski <[EMAIL PROTECTED]> wrote:
>On Fri, 18 May 2001, Keith Owens wrote:
>> I plan to remove CPP and CPPFLAGS, replacing $(CPP) with $(CC) -E
>> throughout and merging CPPFLAGS into [AC]FLAGS. This change will make
>> it much easier to hand
On Fri, 18 May 2001, Keith Owens wrote:
> The distinction between CC and CPP and between [AC]FLAGS and CPPFLAGS
> is very weakly enforced in kbuild. Most code uses CC and [AC]FLAGS,
> even when preprocessing. The extra cflags are almost always
> preprocessor flags, as are [AC]FLAGS_KERNEL.
>
>
The distinction between CC and CPP and between [AC]FLAGS and CPPFLAGS
is very weakly enforced in kbuild. Most code uses CC and [AC]FLAGS,
even when preprocessing. The extra cflags are almost always
preprocessor flags, as are [AC]FLAGS_KERNEL.
I plan to remove CPP and CPPFLAGS, replacing $(CPP)
