make headers_install: .install and ..install.cmd

make headers_install: .install and ..install.cmd

[Geert Uytterhoeven]

	Hi Sam,

When I use `make ARCH=m68k INSTALL_HDR_PATH=/tmp/headers headers_install',
I get lots of `.install' and `..install.cmd' files in /tmp/headers and its
subdirectories.

I'm building the kernel in a separate output directory and run my make command
from there.

Is this intentional?

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

Re: make headers_install: .install and ..install.cmd

[Sam Ravnborg]

On Sun, Dec 14, 2008 at 05:31:08PM +0100, Geert Uytterhoeven wrote:
> 	Hi Sam,
> 
> When I use `make ARCH=m68k INSTALL_HDR_PATH=/tmp/headers headers_install',
> I get lots of `.install' and `..install.cmd' files in /tmp/headers and its
> subdirectories.
> 
> I'm building the kernel in a separate output directory and run my make command
> from there.
> 
> Is this intentional?

Hi Geert.

We use the files .install and ..install.cmd to check if we need to install
the headers again or need to check them again.
And there is no other place to put them than next to the relevant files.
Otherwse we would not do the right thing when exporting to
two different directories from the same repository.

The real fix would be to speed up the install step.
Today we rely on the unifdef tool and a perl scrip for the installation.
Combining the functionality in one C file would most likely
speed up the install process to such a degree that we can do it
unconditionally and then we can get rid of the .install 
and ..install.cmd files.

But noone has written a C program to do that (yet).

	Sam