From: "Pelle Svensson" <pelle2004@gmail.com>
To: "Sam Ravnborg" <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Symbol links to only needed and targeted source files
Date: Wed, 3 Jan 2007 22:14:43 +0100 [thread overview]
Message-ID: <6bb9c1030701031314l1b57bd2brffb61cce68a7174@mail.gmail.com> (raw)
In-Reply-To: <20070103162409.GA30071@uranus.ravnborg.org>
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.
On 1/3/07, Sam Ravnborg <sam@ravnborg.org> wrote:
> On Wed, Jan 03, 2007 at 04:24:11PM +0100, Pelle Svensson wrote:
> > Hi,
> >
> > I would like to set up a directory with only links to the source files
> > I use during the building of the kernel. The development ide/editor
> > will target this directory instead of main source tree. The benefit of this
> > is that I don't need to bother about files that are not included
> > by the configuration.
>
> Anohter approach would be to use a separate output directory.
> In this way you have all generated files in a separate place which
> should solve your needs.
>
> To use it do like this:
>
> make mrproper <= To get a clean starting point
> mkdir ../o
> make O=../o defconfig <= or some other config target
> cd ../o
> make
>
> Se also README.
>
> Sam
>
next prev parent reply other threads:[~2007-01-03 21:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-03 15:24 Pelle Svensson
2007-01-03 16:24 ` Sam Ravnborg
2007-01-03 21:14 ` Pelle Svensson [this message]
2007-01-03 21:39 ` Valdis.Kletnieks
2007-01-03 21:58 ` Sam Ravnborg
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=6bb9c1030701031314l1b57bd2brffb61cce68a7174@mail.gmail.com \
--to=pelle2004@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®