Dne 2.8.2011 21:26, Sam Ravnborg napsal(a): >>> >>> If we do it like this then how about adding this to autoconf.h and avoid the extra file, >>> and the extra flag to gcc? >>> >> That would be intrusive for non-Linux users of kconfig. You would have >> to hardcode a <linux/kconfig.h> in autoconf.h, which mean other >> project would have to either mirror the Linux include tree structure, >> or modify kconfig for the desired include path, if the feature is >> desired at all. As I see it, Linux, through Kbuild, is a user of >> kconfig. > The idea was to entirely skip kconfig.h - and include the code in > autoconf.h verbatim - so no extra file. We could do that. I went for the extra file because it was easier to edit a .h file than to edit a .c file that generates a .h file :). Michal -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
