This is more in the realm of mkdep and the makefiles.
What lets everything down is the fact that mkdep doesn't handle nested
includes. So if you change something in, umm, include/asm/param.h then
your next kernel will mysteriously explode.
Take a look at include/config/* and *.o.flags. It's pretty sneaky. It
appears to provide everything you mention, as long as the dependency
generator can be taught to recur.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/