From: Sam Ravnborg <sam@ravnborg.org>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: Brian Gerst <bgerst@didntduck.org>,
Sam Ravnborg <sam@ravnborg.org>,
Linus Torvalds <torvalds@transmeta.com>,
Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Update fs Makefiles
Date: Tue, 20 May 2003 20:34:03 +0200 [thread overview]
Message-ID: <20030520183403.GA1151@mars.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0305200940130.24017-100000@chaos.physics.uiowa.edu>
On Tue, May 20, 2003 at 09:47:22AM -0500, Kai Germaschewski wrote:
>
> OTOH, 2.4 does only support "-objs", so people may get confused anyway,
> and annoyed about having two different Makefiles to maintain in 2.4 and
> 2.5. Then again, the Makefiles between 2.4 and 2.5 have other differences
> already, and since they're small and rarely changing, maintaining two sets
> isn't so much of a pain.
When we shifted syntax for the kernel configuration people di
not complain about compatibility with 2.4. Why not?
Because it is trivial to maintain two simple files with different
namings:
Config.in for 2.4
Kconfig for 2.5
For the Makefiles we have seen a slow shift in syntax, with more and
more being deprecated. So it is becoming a bit annoying to
maintain 2.4 and 2.5 compatibility in the same file.
Idea:
In 2.5 introduce a new default filename for kbuild Makefiles:
Kmakefile
Then a driver would have:
2.4 Config.help, Config.in and Makefile
2.5 Kconfig and Kmakefile
This would also allow us to do some simplification of the top-level
Makefile by moving the last steps of building vmlinux out to a seperate
Kmakefile - but this is added bonus, the real driver for this change
would be less hassle for 2.4/2.5 compatbility.
Comments?
Sam
The patch is trivial.
===== scripts/Makefile.build 1.36 vs edited =====
--- 1.36/scripts/Makefile.build Thu May 8 22:34:28 2003
+++ edited/scripts/Makefile.build Tue May 20 20:31:33 2003
@@ -11,7 +11,7 @@
include .config
endif
-include $(obj)/Makefile
+include $(if $(wildcard $(obj)/Kmakefile),$(obj)/Kmakefile,$(obj)/Makefile)
include scripts/Makefile.lib
prev parent reply other threads:[~2003-05-20 18:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 0:51 Brian Gerst
2003-05-19 17:02 ` Sam Ravnborg
2003-05-19 21:55 ` Brian Gerst
2003-05-20 14:47 ` Kai Germaschewski
2003-05-20 15:14 ` mikpe
2003-05-20 16:41 ` Kai Germaschewski
2003-05-20 22:54 ` Brian Gerst
2003-05-20 15:33 ` Roman Zippel
2003-05-20 16:38 ` Kai Germaschewski
2003-05-20 18:34 ` Sam Ravnborg [this message]
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=20030520183403.GA1151@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=bgerst@didntduck.org \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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®