Already covered by my 2.5 makefile rewrite[1] which has explicit
support for third party kernel source. Shadow trees are designed
specifically to handle this problem. I don't see the point of adding a
script which will only be used in 2.4, especially when the vendors
would have to change their tarball format for 2.5 formats.
(3) The kernel is constructed from multiple source trees and built in a
separate object tree.
As for (2) you have a separate object directory for each set of
config options. But instead of manually building a single source
tree from various patches, the patch sets are kept separate and
kbuild 2.5 logically constructs a single kernel source tree from
the various source trees. This is called a shadow tree system
because the patch sets shadow the main kernel source tree.
[1] http://sourceforge.net/projects/kbuild
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/