From: Sam Ravnborg <sam@ravnborg.org>
To: Pelle Svensson <pelle2004@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Symbol links to only needed and targeted source files
Date: Wed, 3 Jan 2007 22:58:50 +0100 [thread overview]
Message-ID: <20070103215850.GA32137@uranus.ravnborg.org> (raw)
In-Reply-To: <6bb9c1030701031314l1b57bd2brffb61cce68a7174@mail.gmail.com>
On Wed, Jan 03, 2007 at 10:14:43PM +0100, Pelle Svensson wrote:
> Hi Sam,
>
> You misunderstand me I think, I already using a separate output directory.
> What I like to do is a separate 'source tree' with only valid files
> for my configuration. In that way, when I use grep for instance,
> I would only hit valid files and not 50 other files which are
> not in the current build configuration.
I see.
There is nothing in kbuild that will help you to achieve this.
If you build the kernel and parse all .*.cmd files then
you can build a complete list of files used and create your
symlinked tree.
But then you need a fully build kernel to do so.
I see no easy way to get the info without building the kernel
and if we do this only as a preprocessing step then we will
most likely not integrate it in kbuild since the user base will
be small. But if you hack up something lets take a look at it.
Sam
next prev parent reply other threads:[~2007-01-03 21:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-03 15:24 Symbol links to only needed and targeted source files Pelle Svensson
2007-01-03 16:24 ` Sam Ravnborg
2007-01-03 21:14 ` Pelle Svensson
2007-01-03 21:39 ` Valdis.Kletnieks
2007-01-03 21:58 ` Sam Ravnborg [this message]
2007-01-03 22:35 ` Pelle Svensson
2007-01-05 12:00 ` Michael Tokarev
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=20070103215850.GA32137@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pelle2004@gmail.com \
/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.