From: Larry McVoy <lm@bitmover.com>
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 12:31:15 -0800 [thread overview]
Message-ID: <20021119123115.C16028@work.bitmover.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1021119151730.5943A-100000@chaos.analogic.com>; from root@chaos.analogic.com on Tue, Nov 19, 2002 at 03:22:45PM -0500
On Tue, Nov 19, 2002 at 03:22:45PM -0500, Richard B. Johnson wrote:
> On Tue, 19 Nov 2002, Sam Ravnborg wrote:
>
> > Based on some initial work by Kai Germaschewski I have made a
> > working prototype of separate obj/src tree.
> >
> > Usage example:
> > #src located in ~/bk/linux-2.5.sepobj
> > mkdir ~/compile/v2.5
> > cd ~/compile/v2.5
> > sh ../../kb/v2.5/kbuild
>
> [SNIPPED...]
>
> I have a question; "What problem is this supposed to solve?"
> This looks like a M$ism to me. Real source trees don't
> look like this. If you don't have write access to the source-
> code tree, you are screwed on a real project anyway. That's
> why we have CVS, tar and other tools to provide a local copy.
It can be really nice to maintain a bunch of different architectures at
the same time from the same tree. It also makes it really easy to
"clean" a tree.
On the other hand, I do wonder whether ccache could be used to get the
same effect. Sam?
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2002-11-19 20:24 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
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 [this message]
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=20021119123115.C16028@work.bitmover.com \
--to=lm@bitmover.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
--cc=sam@ravnborg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.