From: Sam Ravnborg <sam@ravnborg.org>
To: Linus Torvalds <torvalds@osdl.org>,
akpm@ravnborg.org, Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: linux-kernel@vger.kernel.org
Subject: kbuild: Separate ouput directory support
Date: Tue, 19 Aug 2003 23:41:44 +0200 [thread overview]
Message-ID: <20030819214144.GA30978@mars.ravnborg.org> (raw)
The following set of patches introduce support for
separate output directory when building a kernel.
Typical usage is building several kernels with different configurations -
but based on the same kernel src.
Consider the following setup:
/home/sam/bk/linux-2.6 <= kernel src
/home/sam/kernel/mars <= My workstation
/home/sam/kernel/defconfig <= defconfig for compiletime testing
Then in order to handle the two different configurations I just have to do:
cd /home/sam/bk/linux-2.6
make O=../../kernel/mars
And the same for the defconfig version.
All output files are stored in the output directory, including .config.
[Thanks to Roman Zippel which made this loong time ago in kconfig].
The patch has been in existence in several months but only lately becoming
in a suitable state ready for inclusion. It is developed based on an initial
concept made by Kai Germaschewski, but refined a lot since then.
It works with a kernel based on default configuration (make defconfig).
It is divided up in the following parts:
core the kbuild changes to support separate output directory
ieee Fix in ieee Makefile
i386 Fix in i386 Makefiles + new syntax enabled for always
This was required because i386 had an executable located in
a subdirectory.
include Fixes for errornous include paths, and one place where a generated
.c file references a .h file in the kernel tree.
Please pull from
bk pull bk://linux-sam.bkbits.net/kbuild
Patches follows this mail.
Sam
next reply other threads:[~2003-08-19 21:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-19 21:41 Sam Ravnborg [this message]
2003-08-19 21:53 ` Jeff Garzik
2003-08-19 21:56 ` Sam Ravnborg
2003-08-19 22:13 ` Mike Fedyk
2003-08-21 3:09 ` Chris Friesen
2003-08-21 9:42 ` Geert Uytterhoeven
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=20030819214144.GA30978@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@ravnborg.org \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
Powered by JetHome