LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Chris Smith" <smitty1elkml@gmail.com>
To: "Pelle Svensson" <pelle2004@gmail.com>
Cc: linux-kernel@vger.kernel.org, "Sam Ravnborg" <sam@ravnborg.org>
Subject: Re: Skeleton, Makefile extension - Separate source tree with only valid source files
Date: Mon, 15 Jan 2007 07:43:53 -0500	[thread overview]
Message-ID: <9b53a56d0701150443o7213ef6at4f877cca0d4aa377@mail.gmail.com> (raw)
In-Reply-To: <6bb9c1030701150135x173f95c0lb67247b641137367@mail.gmail.com>

On 1/15/07, Pelle Svensson <pelle2004@gmail.com> wrote:
> Did some hacks to the Makefile which might be of interest for those who
> feel like there are too many source files in the Linux tree. Running following
> make will create a separate directory including only the files which are
> active i.e. they are include in the final build configuration.
>
> source = /home/john/src/linux-2.6.20
> build_dir = /home/john/src/linux-2.6.20-build
> edit_dir = /home/john/src/linux-2.6.20-edit
>
> cd $(source)
> make O=$(build_dir) ACTIVE_SRC=$(edit_dir) active_srctree
>
> Links will be create in $(edit_dir) and what ever IDE that are in use for
> editing should target the $(edit_dir). The good thing is that grep will only
> hit valid files not 50 other files which are not in my interest.
>
>
> Due to lack of time this is not complete. Phrasing the dependency need to
> be added for all the include files.
>
[snip]

Another interesting thought might be to have kbuild run all of the
files through the pre-processor, then indent.
Then one could have a clearer view of the kernel object as actually
seen by the compiler.
Thanks, Pelle.
--Chris

      reply	other threads:[~2007-01-15 12:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-15  9:35 Pelle Svensson
2007-01-15 12:43 ` Chris Smith [this message]

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=9b53a56d0701150443o7213ef6at4f877cca0d4aa377@mail.gmail.com \
    --to=smitty1elkml@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pelle2004@gmail.com \
    --cc=sam@ravnborg.org \
    --subject='Re: Skeleton, Makefile extension - Separate source tree with only valid source files' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).