# HG changeset patch # User "Yann E. MORIN" # Date 1226598916 0 # Node ID dc17e615de2cdb9fe1ea9172989589b9731070cf # Parent b534a133daf45d5a681577888e5321e177d59553 Merge 1199 and 1200 from /devel/YEM-build_host_target_cleanup: - Allow hand-indentation in the kconfig prompts - Start documenting the kconfig deviations from the kernel's version /trunk/kconfig/menu.c | 10 8 2 0 ++++++++-- /trunk/docs/overview.txt | 6 6 0 0 ++++++ 2 files changed, 14 insertions(+), 2 deletions(-) diff -r b534a133daf4 -r dc17e615de2c docs/overview.txt --- a/docs/overview.txt Thu Nov 13 17:34:44 2008 +0000 +++ b/docs/overview.txt Thu Nov 13 17:55:16 2008 +0000 @@ -524,6 +524,12 @@ The kconfig language is a hacked version, vampirised from the Linux kernel (http://www.kernel.org/), and (heavily) adapted to my needs. +The list of the most notable changes (at least the ones I remember) follows: +- the CONFIG_ prefix has been replaced with CT_ +- a leading | in prompts is skipped, and subsequent leading spaces are not + trimmed +- otherwise leading spaces are silently trimmed + The kconfig parsers (conf and mconf) are not installed pre-built, but as source files. Thus you can have the directory where crosstool-NG is installed, exported (via NFS or whatever) and have clients with different architectures diff -r b534a133daf4 -r dc17e615de2c kconfig/menu.c --- a/kconfig/menu.c Thu Nov 13 17:34:44 2008 +0000 +++ b/kconfig/menu.c Thu Nov 13 17:55:16 2008 +0000 @@ -128,8 +128,14 @@ prop->visible.expr = menu_check_dep(dep); if (prompt) { - if (isspace(*prompt)) { - prop_warn(prop, "leading whitespace ignored"); + /* For crostool-NG, a leading pipe followed with spaces + * means that pipe shall be removed, and the spaces should + * not be trimmed. + */ + if (*prompt == '|') + prompt++; + else if (isspace(*prompt)) { + /* Silently trim leading spaces */ while (isspace(*prompt)) prompt++; }