From: Sam Ravnborg <sam@ravnborg.org>
To: R S-P Chan <rspchan@dso.org.sg>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Does kbuild 2.5 support separate obj/src trees
Date: Thu, 10 Apr 2003 17:26:35 +0200 [thread overview]
Message-ID: <20030410152635.GA1577@mars.ravnborg.org> (raw)
In-Reply-To: <3E939034.8010106@dso.org.sg>
On Wed, Apr 09, 2003 at 11:15:00AM +0800, R S-P Chan wrote:
> Haven't been building kernels for a while but the Makefile contains
> srctree/objtree variables - so does kbuild 2.5 now support
> separate obj/src trees? Tks.
Not yet.
I have posted a patch enabling this a couple of times, but it has not
mainstream kernel yet :-(
There is people that request this feature, and it is doable - with some
annoying restrictions. The main issue is that the kernel src shall be
free of generated files when compiling for a separate objtree.
I got limited feedback on the implementataion so far.
The patch will most likely be updated during easter.
Sam
prev parent reply other threads:[~2003-04-10 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-09 3:15 Does kbuild 2.5 support separate obj/src trees R S-P Chan
2003-04-10 15:26 ` 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=20030410152635.GA1577@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rspchan@dso.org.sg \
/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