What is needed to build an external module
In a private mail Dev Mazumdar suggested to create a system for building external modules without the necessity to have the full kernel source available.
I decided to take this to LKML since it may be a questions other people had.
The reason why one must use the kbuild infrastructure when building external modules are the CONFIG choices that either impact gcc options or the include files.
If a seperate system for buiding modules were made that part should be copied over for each and every change, and only one particular version of the 'building external modules' would be compatible with a given kernel version. So having a seperate system is a no-go.
What one should realize what is actually needed to build an external module.
A full copy of:
root of kernel srcinclude/scripts/
and a copy of the Makefile for the selected architecture. Thats all needed to build a well behaving external module. This could very well be what a distribution places in /lib/modules/linux-<version>/build
and not a full kernel tree.
Hope this clarifies,
Sam