From: Keith Owens <kaos@ocs.com.au>
To: brendan.simon@bigpond.com
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: touch commands in Makefiles
Date: Sat, 26 Jan 2002 21:38:58 +1100 [thread overview]
Message-ID: <20898.1012041538@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Fri, 25 Jan 2002 16:54:39 +1100." <3C50F31F.1090302@bigpond.com>
On Fri, 25 Jan 2002 16:54:39 +1100,
Brendan J Simon <brendan.simon@bigpond.com> wrote:
>Why are header file touched in Makefiles ?
To handle the two level dependencies on CONFIG options. bar.c depends
on foo.h which depends on CONFIG_BLIP. Change CONFIG_BLIP and the
Makefiles touch foo.h which in turn recompiles bar.c.
Yes, it sucks with source repositories. Which is why kbuild 2.5
completely removes this "feature", with kbuild 2.5 you can build from a
read only file system.
>You then tell it which files you intend to modify and it
>will check those files out as read-write to the local sandbox.
Even easier with kbuild 2.5, it has shadow trees. You keep the base
read only, copy the files to modify to a separate tree and kbuild 2.5
logically merges all the files.
http://sourceforge.net/projects/kbuild/
next prev parent reply other threads:[~2002-01-26 10:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-25 5:54 Brendan J Simon
2002-01-26 10:38 ` Keith Owens [this message]
2002-01-28 8:17 ` Marian Jancar
2002-01-28 8:20 ` Keith Owens
2002-01-27 1:29 Peter Samuelson
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=20898.1012041538@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=brendan.simon@bigpond.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®