From: Sam Ravnborg <sam@ravnborg.org>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net,
Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Subject: Re: [RFC/CFT] Separate obj/src dir
Date: Tue, 19 Nov 2002 21:54:30 +0100 [thread overview]
Message-ID: <20021119205430.GC15161@mars.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.3.95.1021119153545.6004A-100000@chaos.analogic.com>
On Tue, Nov 19, 2002 at 03:46:28PM -0500, Richard B. Johnson wrote:
> Different configurations are handled with different ".config"
> files.
And different .config files results in different kernels.
Please note that .config files are also located in OBJTREE.
Cosider something like the following:
~/bk/linux-2.5
~/compile/arm <= Used to check that the kernel compiles for ARM
~/compile/allmod <= My config with a lot of modules
~/compile/machine <= The config I use on my machine
~/compile/work <= That's my sandbox
All configurations share the same src.
During the last copule of days we have seen some header file
clean-ups. It would have been nice if they tried compiling in
all four configurations listed above.
But if I switch .config then it is often a recompile of everything,
whereas the above setup can minimize it.
The header file cleanup is maybe not the best example because touching
a few key header files requires recompilation of everything anyway.
But my point is that there is a good use of different configurations
based on the same src.
Others that have asked for separate obj dir may step in here,
explaining why they thougt it was good.
Sam
next prev parent reply other threads:[~2002-11-19 20:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-19 20:11 [RFC/CFT] Separate obj/src dir Sam Ravnborg
2002-11-19 20:22 ` Richard B. Johnson
2002-11-19 20:29 ` Sam Ravnborg
2002-11-19 20:46 ` Richard B. Johnson
2002-11-19 20:50 ` Kai Germaschewski
2002-11-19 20:54 ` Sam Ravnborg [this message]
2002-11-19 21:37 ` David Woodhouse
2002-11-20 4:04 ` Miles Bader
2002-11-19 21:55 ` Brad Hards
2002-11-19 21:01 ` Daniel Jacobowitz
2002-11-19 21:19 ` Geert Uytterhoeven
2002-11-21 16:54 ` Henning P. Schmiedehausen
2002-11-19 20:31 ` Larry McVoy
2002-11-19 20:43 ` Sam Ravnborg
2002-11-19 20:48 ` Kai Germaschewski
2002-11-19 21:57 ` Sam Ravnborg
2002-11-21 16:53 ` Henning P. Schmiedehausen
2002-11-19 20:51 ` Brian Jackson
2002-11-19 22:05 ` Sam Ravnborg
2002-11-20 6:37 ` Simon Fowler
[not found] ` <mailman.1037774521.18360.linux-kernel2news@redhat.com>
2002-11-20 7:06 ` Pete Zaitcev
2002-11-20 13:10 ` [RFC/CFT] " Alex Riesen
2002-11-20 13:14 ` Alex Riesen
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=20021119205430.GC15161@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.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