Hi, Many projects are using Kconfig's derivate as their configuration UI. Some of these projects change the default "CONFIG_" prefix for something else. It obliges them to dig in the sources to find and replace all occurences and associated constant. Same goes for package name where when the project ship a C library, messages about a kernel may not be welcome. OOTH, a project may want to limit its changes to be able to re-sync with the kernel's Kconfig and benefits from latest features and bug fixes. The two next patches factorizes Kconfig's prefix and package name to generic macros defined in `scripts/kconfig/lkc.h'. This allow projects to easily tune Kconfig for their need with trivial source modification. There may have been similar patches in the past, in which case this message can be silently discarded :) any comments appreciated ! - Arnaud Arnaud Lacombe (2): kbuild: genericizes package name kbuild: genericizes kbuild's config prefix scripts/kconfig/conf.c | 12 ++++---- scripts/kconfig/confdata.c | 48 +++++++++++++++++----------------- scripts/kconfig/gconf.c | 4 +- scripts/kconfig/lkc.h | 7 ++++- scripts/kconfig/mconf.c | 44 ++++++++++++++++---------------- scripts/kconfig/menu.c | 2 +- scripts/kconfig/nconf.c | 40 ++++++++++++++--------------- scripts/kconfig/qconf.cc | 6 ++-- scripts/kconfig/zconf.tab.c_shipped | 2 +- scripts/kconfig/zconf.y | 2 +- 10 files changed, 85 insertions(+), 82 deletions(-) -- 1.7.2.30.gc37d7.dirty -- 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
