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.
>
> 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 handle implicit dependencies in kbuild 2.5.
I don't see this, can you explain it further? CFLAGS is set to
$(CPPFLAGS) + compilation flags, whereas the preprocessing of course only
needs $(CPPFLAGS). Well, currently it's not done cleanly at all, i.e.
-D__MODULE__ -include ... etc. are added directly to the command line and
aren't part of $(CPPFLAGS), but that's fixable.
> Can anybody see a good reason to retain CPP and CPPFLAGS in kbuild?
I don't think anybody is using anything but gcc -E for preprocessing, so
it won't break anything. But what I do not see is the good reason to
remove this logical separation between preprocessing and compilation, and
that's the question which should be asked IMO.
--Kai
_______________________________________________
kbuild-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/kbuild-devel
