kbuild 2.5 question about generated files

kbuild 2.5 question about generated files

[David Mansfield]

I've read the release announcements about the new kbuild and it sounds
like it will be possible to build from kernel sources that reside on a
read-only filesystem?  Is that the case?

In other words, it will be possible to build the kernel in such a way that
NO generated files (including all those generated .h files) get put into
the kernel tree proper?

I'm concerned about the unfixable problems that we had discussed a while
ago about the 'dontdiff' file that someone was maintaining, that listed
some of the generated files (or file patterns) and that in its current
form, such a file CANNOT be made due to name conflics between generated
and non-generated files.

The problem with the 'dontdiff', in case you have forgotten, is that
programs like CVS and diff don't accept path qualifications in the exclude
list, just filename patterns, and there are some conflicts (esp. version.h
IIRC).

David



-- 
David Mansfield                                           (718) 963-2020
david@ultramaster.com
Ultramaster Group, LLC                               www.ultramaster.com

Re: kbuild 2.5 question about generated files

[Keith Owens]

On Mon, 10 Sep 2001 11:23:36 -0400 (EDT), 
David Mansfield <david@ultramaster.com> wrote:
>I've read the release announcements about the new kbuild and it sounds
>like it will be possible to build from kernel sources that reside on a
>read-only filesystem?  Is that the case?

Yes.  Run with separate source and object directories and nothing
expect last access time stamp is updated in the source directory.