From: Sam Ravnborg <sam@ravnborg.org>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 9/12] kbuild: mips use generic asm-offsets.h support
Date: Sat, 10 Sep 2005 22:48:17 +0200 [thread overview]
Message-ID: <20050910204817.GH29334@mars.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0509102217270.3743@scrub.home>
Hi Roman.
> > kbuild looks for the Kbuild file before it looks for Makefile.
> > In a desire to move some of the functionality away form the top-level
> > Makefile and in to a kbuild file this is needed.
>
> Why don't you put it into scripts/Makefile...?
Because it does not build a build-support program.
That would be the last place where one would look for
rules to build asm-offsets.h for example.
When the functionalty to start the recursive build of all kernel
directories are moved to top-level Kbuild the location in the
top-level directory makes even more sense.
Same goes when the post processing steps are moved to the top-level
Kbuild file. Here we again will benefit form having the full kbuild
funtionality available.
> > The Kbuild file in the top-level directory will take
> > over more and more functionality from the top-level
> > Makefile to the extent that I hope to end up with two
> > readable files.
>
> If the top-level Makefile gets to big, we can move things into scripts/,
> that's really no reason to start using Kbuild, in the end it's still a
> Makefile and I'd prefer to call it like that.
A makefile is a file that does something intelligent when used as input
to make. It is long time since this property did not hold for the
kernel.
The Kbuild name is a much more natural name in the respect that it
tells you this file contain kbuild info. So one know when browsing
a directory structure that a Kbuild file is input to kbuild, and follow
a much more strict syntax than ordinary Makefiles.
Sam
next prev parent reply other threads:[~2005-09-10 20:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-09 22:41 [PATCH 1/12] kbuild: full dependency check on asm-offsets.h Sam Ravnborg
2005-09-09 22:41 ` [PATCH 2/12] kbuild: h8300,m68knommu,sh,sh64 use generic asm-offsets.h support Sam Ravnborg
2005-09-09 22:41 ` [PATCH 3/12] kbuild: arm26,sparc use generic asm-offset support Sam Ravnborg
2005-09-09 22:41 ` [PATCH 4/12] kbuild: m68k,parisc,ppc,ppc64,s390,xtensa use generic asm-offsets.h support Sam Ravnborg
2005-09-09 22:41 ` [PATCH 5/12] kbuild: arm - " Sam Ravnborg
2005-09-09 22:41 ` [PATCH 6/12] kbuild: alpha,x86_64 " Sam Ravnborg
2005-09-09 22:41 ` [PATCH 7/12] kbuild: v850 " Sam Ravnborg
2005-09-09 22:41 ` [PATCH 8/12] kbuild: ia64 " Sam Ravnborg
2005-09-09 22:41 ` [PATCH 9/12] kbuild: mips " Sam Ravnborg
2005-09-09 22:41 ` [PATCH 10/12] kbuild: cris " Sam Ravnborg
2005-09-09 22:41 ` [PATCH 11/12] kbuild: frv,m32r,sparc64 introduce fake asm-offsets.h file Sam Ravnborg
2005-09-09 22:41 ` [PATCH 12/12] kbuild: um fix so it compile with generic asm-offsets.h support Sam Ravnborg
2005-09-10 19:15 ` [PATCH 9/12] kbuild: mips use " Roman Zippel
2005-09-10 19:30 ` Sam Ravnborg
2005-09-10 20:26 ` Roman Zippel
2005-09-10 20:48 ` Sam Ravnborg [this message]
2005-09-10 21:09 ` Roman Zippel
2005-09-11 2:09 ` Yoichi Yuasa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050910204817.GH29334@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®