On Tue, Nov 19, 2002 at 02:51:54PM -0600, Brian Jackson wrote:
> Sam Ravnborg writes:
>
> <snip>
> >Another drawback is that when a .h file exist in the
> >SRCTREE but not in the OBJTREE the generated dependencies
> >will point out the .h file located in SRCTREE.
> >This happens for generated .h files, and therefore a simple
> >check is made in kbuild to check that the SRCTREE is
> >cleaned/mrpropered.
>
> I wonder how hard it would be to do this for other files types. It would be
> sort of handy to be able to copy a single file out of the source tree into
> the build tree, and have the build use the copy in the build tree. Example:
> you want to test a one liner in drivers/scsi/sd.c, you could just copy sd.c
> into the build tree, and make the change and test it out. That could be a
> huge space savings. That would help out those of us that are stuck with
> tiny hard drives in our laptops :)
>
For that you probably want to use the hardlinked trees approach.
Just do a cp -al linux-2.5 scratch; then change your file and build
from the copy.
Simon
-- PGP public key Id 0x144A991C, or http://himi.org/stuff/himi.asc (crappy) Homepage: http://himi.org doe #237 (see http://www.lemuria.org/DeCSS) My DeCSS mirror: ftp://himi.org/pub/mirrors/css/
This archive was generated by hypermail 2b29 : Sat Nov 23 2002 - 22:00:30 EST