Re: [PATCH] kbuild: Improve Kernel build with separated output

[Sam Ravnborg <sam@ravnborg.org>]

On Tue, Jun 22, 2004 at 06:04:28PM -0400, Ricky Beam wrote:
> On Tue, 22 Jun 2004, Sam Ravnborg wrote:
> >1) A Makefile is generated in the output directory allowing
> >   one to execute make in both the source and the output directory.
> 
> I would vote against doing that.  Or at the very least don't overwrite one
> that might already be there.  I, for one, have a very specific makefile in
> my build (object) directories.  Anyone sufficiently skilled to be building
> kernels outside the source tree, and/or those with the specific need to be
> doing so will already have makefiles and/or shell scripts to suit their
> needs.  Making the option a user specified target ala "make makefiles"
> would be a better/safer choice; if the user wants or needs a makefile in
> their object directory, then they have a simple option to make themselves
> one -- no knowledge of GNU Make necessary.

You cold just rename your Makefile to makefile. Then GNU Make will select that one
as first choice.

Today kbuild unconditionally overwrite the Makefile, because it depends on the following:
- Top level Makefile (VERSION)
- scripts/mkmakefile script
- Source directory
- Output directory

In total too many factors to check for so the more brutal approach used.

Do you use your specific Makefile for something others could benefit from?

	Sam