When we shifted syntax for the kernel configuration people di
not complain about compatibility with 2.4. Why not?
Because it is trivial to maintain two simple files with different
namings:
Config.in for 2.4
Kconfig for 2.5
For the Makefiles we have seen a slow shift in syntax, with more and
more being deprecated. So it is becoming a bit annoying to
maintain 2.4 and 2.5 compatibility in the same file.
Idea:
In 2.5 introduce a new default filename for kbuild Makefiles:
Kmakefile
Then a driver would have:
2.4 Config.help, Config.in and Makefile
2.5 Kconfig and Kmakefile
This would also allow us to do some simplification of the top-level
Makefile by moving the last steps of building vmlinux out to a seperate
Kmakefile - but this is added bonus, the real driver for this change
would be less hassle for 2.4/2.5 compatbility.
Comments?
Sam
The patch is trivial.
===== scripts/Makefile.build 1.36 vs edited =====
--- 1.36/scripts/Makefile.build Thu May 8 22:34:28 2003
+++ edited/scripts/Makefile.build Tue May 20 20:31:33 2003
@@ -11,7 +11,7 @@
include .config
endif
-include $(obj)/Makefile
+include $(if $(wildcard $(obj)/Kmakefile),$(obj)/Kmakefile,$(obj)/Makefile)
include scripts/Makefile.lib
-
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/