From: Greg Banks <gnb@alphalink.com.au>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>,
mec@shout.net, kbuild-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [kbuild-devel] [PATCH] kconfig: menuconfig and config uses $objtree
Date: Fri, 28 Jun 2002 18:07:45 +1000 [thread overview]
Message-ID: <3D1C1951.987E1FF8@alphalink.com.au> (raw)
In-Reply-To: 20020628001452.A14485@mars.ravnborg.org
Sam Ravnborg wrote:
>
> In order to prepare for separate obj and src trees make use of $objtree
> within scripts/Menuconfig and scripts/Configure.
> All temporary and all result files are located in directory pointed at
> by $objtree.
>
> This functionality is foreseen useful for both current kbuild and kbuild-2.5
Interesting, but there's an alternative approach. Let the scripts dump
any files they like into the current directory, but move the current
directory to be the *object* directory not the source directory. Then
all you need to change are the places where the arch config.in files are
initially included, and to override the "source" statement to look relative
to $srctree not the current directory. That last can be done like this:
xsource ()
{
builtin source $srctree/$1
}
shopt -s expand_aliases
alias source=xsource
So the scripts do not even need to know about object directory and source
directory, they only need to know that there is a source directory which
can be separate from the current directory. This behaviour is closer to
the way autoconf behaves with a separate object directory.
Greg.
--
the price of civilisation today is a courageous willingness to prevail,
with force, if necessary, against whatever vicious and uncomprehending
enemies try to strike it down. - Roger Sandall, The Age, 28Sep2001.
next prev parent reply other threads:[~2002-06-28 8:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-27 22:14 [PATCH] kconfig: menuconfig and config uses $objtree Sam Ravnborg
2002-06-28 2:19 ` Keith Owens
2002-06-28 17:28 ` Sam Ravnborg
2002-06-29 1:50 ` Keith Owens
2002-06-29 7:26 ` Sam Ravnborg
2002-06-29 8:23 ` Keith Owens
2002-06-30 9:31 ` [kbuild-devel] " Greg Banks
2002-06-29 15:36 ` Roman Zippel
2002-06-28 8:07 ` Greg Banks [this message]
2002-06-28 8:58 ` [kbuild-devel] " Keith Owens
2002-06-28 9:16 ` Greg Banks
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=3D1C1951.987E1FF8@alphalink.com.au \
--to=gnb@alphalink.com.au \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mec@shout.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox