Hi Roman.
> > Kbuild | 9 ++++++++-
>
> What's that file good for?
kbuild looks for the Kbuild file before it looks for Makefile.
In a desire to move some of the functionality away form the top-level
Makefile and in to a kbuild file this is needed.
In this particular case the Kbuild file is located in the top-level
directory because it is used to read a file down in arch/$(ARCH)
and store the result file in include/asm-$(ARCH).
Here it come in handy that kbuild prefer the Kbuild name, since
it would not be good to try to use the top-level Makefile as
a kbuild file. It is full of conditionals and one more
spanning-the-whole-file conditional was too ugly.
It also come in handy that the full kbuild functionality is
available making it possible to do full dependency checking.
The Kbuild file in the top-level directory will take
over more and more functionality from the top-level
Makefile to the extent that I hope to end up with two
readable files.
Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |