From: Bernd Petrovitsch <bernd@firmix.at>
To: root@chaos.analogic.com
Cc: "Robert P. J. Day" <rpjday@mindspring.com>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: how to configure/build a kernel in a separate directory?
Date: Mon, 07 Jun 2004 23:52:28 +0200 [thread overview]
Message-ID: <1086645148.8887.6.camel@gimli.at.home> (raw)
In-Reply-To: <Pine.LNX.4.53.0406071710540.1435@chaos>
On Mon, 2004-06-07 at 23:31, Richard B. Johnson wrote:
> On Mon, 7 Jun 2004, Robert P. J. Day wrote:
[...]
> > (i originally posted this to the "make" mailing list, but i figured
> > someone here *must* have done this before.)
Not only here. And yes.
> > is there an easy way to configure/build one or both of a 2.4 and 2.6
> > kernel in a totally separate directory from the source directory itself?
> >
> > i'd like to have a totally pristine ("make mrproper"ed) source tree,
> > write-protected, readable by all, so that several developers can
> > independently configure and build their own kernels without stepping on
> > each other. currently, they all check out their own copy of the source
> > via CVS, which starts to take up a lot of space.
> >
> > obviously, it would be great if they could all set up some kind of build
> > structure where they could do their own configuration and build in their
> > personal work directories, so that *all* generated results (header files,
> > object files, etc.) are placed in their work directory -- nothing should
> > be generated in the kernel source tree itself.
> >
> > i'm suspecting that, if there are solutions, they will be different from
> > 2.4 to 2.6, so i'll take whatever solutions i can get. others have
> > suggested using gnu make in combination with "VPATH", but i'm not sure
> > that's going to work, as VPATH deals strictly with pre-requisites in other
> > directories, not executable programs like scripts.
VPATH works for make, but not for other scripts and tools.
> I would make a script that creates a symbolic-link of all the
> source-files and headers. To get it right, put the source on
> a r/o file-system as a start. It's a lot of work.
No, lndir exists (somewhere in X11 or XFree86 IIRC).
Just make a sym-linked copy of the (read-only) pristine source
directory.
Voila. And quite easy.
> `find . -name "*.[chS]"` should get all the sources, but there
> are some scripts you will have to hunt for.
No, just take all files which are there. It is simple and works.
Bernd
--
Firmix Software GmbH http://www.firmix.at/
mobil: +43 664 4416156 fax: +43 1 7890849-55
Embedded Linux Development and Services
next prev parent reply other threads:[~2004-06-07 21:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-07 21:00 Robert P. J. Day
2004-06-07 21:31 ` Richard B. Johnson
2004-06-07 21:52 ` Bernd Petrovitsch [this message]
2004-06-07 21:33 ` Sean Neakums
2004-06-07 23:28 ` Robert P. J. Day
2004-06-07 21:36 ` Sam Ravnborg
2004-06-08 6:32 ` Michelle Konzack
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=1086645148.8887.6.camel@gimli.at.home \
--to=bernd@firmix.at \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
--cc=rpjday@mindspring.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®