public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.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: [PATCH] kconfig: menuconfig and config uses $objtree
Date: Fri, 28 Jun 2002 12:19:00 +1000	[thread overview]
Message-ID: <31443.1025230740@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Fri, 28 Jun 2002 00:14:52 +0200." <20020628001452.A14485@mars.ravnborg.org>

On Fri, 28 Jun 2002 00:14:52 +0200, 
Sam Ravnborg <sam@ravnborg.org> 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

Wrong approach.  This messes up kbuild 2.5.  The config tools should
not know where the files are being read from or written to, you have
hard coded knowledge about the tree structure into the config system.

kbuild 2.5 handles this by constructing a set of symlinks then invoking
the configure system under those symlinks, followed by copying any
results to their destination.  The symlink tree completely isolates
the config system from any knowledge of where its inpuuts and outputs
really are, everything looks local.

You have a 750+ line patch to imbed tree knowledge into configure, that
knowledge will have to be duplicated for any new CML tools.  kbuild 2.5
does it in a few lines of scripts/Makefile-2.5 which automatically
works for any new CML code.


  reply	other threads:[~2002-06-28  2:16 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 [this message]
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 ` [kbuild-devel] " Greg Banks
2002-06-28  8:58   ` 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=31443.1025230740@ocs3.intra.ocs.com.au \
    --to=kaos@ocs.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