Random thoughts. I haven't actually tested the patch yet, so feel
free to ignore me. (:
[Kai Germaschewski]
> i.e. the current working directory remains the top dir for all
> times.
Which top dir, src or obj? Most end users will expect obj topdir.
More on that below.
> So gcc/ld/.. are now
Hi,
I'd appreciate to get comments on the appended patch. It's mostly cleanups
and the like, but the interesting part is the last cset, which is actually
fairly small:
14 files changed, 64 insertions(+), 47 deletions(-)
The build process remains recursive, but it changes the recursion
from
On Oct 02, 2002 21:59 -0500, Kai Germaschewski wrote:
> The build process remains recursive, but it changes the recursion
> from
> make -C subdir
> to
> make -f subdir/Makefile
>
> i.e. the current working directory remains the top dir for all times. So
> gcc/ld/.. are now called f
[Kai Germaschewski]
> I've been thinking about doing something like this a couple of
> times. The reasons I didn't actually do it yet was that include
> $(TOPDIR)/Rules.make was kind of a separator between automatically
> handled stuff and additional hand-made rules for special cases.
Well, OK -
On Wed, 2 Oct 2002, Peter Samuelson wrote:
> Almost all kernel makefiles have to include $(TOPDIR)/Rules.make
> explicitly. 3/4 of the time, this is done at the end of the file.
> This patch lets you omit the include line in that case. (You still to
> include Rules.make explicitly if you have s
Almost all kernel makefiles have to include $(TOPDIR)/Rules.make
explicitly. 3/4 of the time, this is done at the end of the file.
This patch lets you omit the include line in that case. (You still to
include Rules.make explicitly if you have special make rules.)
As a positive side effect, we
