lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6bb9c1030701031314l1b57bd2brffb61cce68a7174@mail.gmail.com>
Date:	Wed, 3 Jan 2007 22:14:43 +0100
From:	"Pelle Svensson" <pelle2004@...il.com>
To:	"Sam Ravnborg" <sam@...nborg.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Symbol links to only needed and targeted source files

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@...nborg.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
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ