From ec57b1f3da0f0e2f348574a11a62b2c2c58cec42 Mon Sep 17 00:00:00 2001 From: Ulf Magnusson Date: Fri, 20 Jul 2018 21:31:00 +0200 Subject: Mention KCONFIG_STRICT in the README Also fix up Kconfig.__init__() docstring to say that KCONFIG_STRICT needs to be "y". --- kconfiglib.py | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) (limited to 'kconfiglib.py') diff --git a/kconfiglib.py b/kconfiglib.py index 8b798b4..988c319 100644 --- a/kconfiglib.py +++ b/kconfiglib.py @@ -585,12 +585,12 @@ class Kconfig(object): KconfigError on syntax errors. Note that Kconfig files are not the same as .config files (which store configuration symbol values). - If KCONFIG_STRICT is set in the environment (to any value), warnings - will be generated for all references to undefined symbols within - Kconfig files. The reason this isn't the default is that some projects - (e.g. the Linux kernel) use multiple Kconfig trees (one per - architecture) with many shared Kconfig files, leading to some safe - references to undefined symbols. + If the environment variable KCONFIG_STRICT is set to "y", warnings will + be generated for all references to undefined symbols within Kconfig + files. The reason this isn't the default is that some projects (e.g. + the Linux kernel) use multiple Kconfig trees (one per architecture) + with many shared Kconfig files, leading to some safe references to + undefined symbols. KCONFIG_STRICT relies on literal hex values being prefixed with 0x/0X. They are indistinguishable from references to undefined symbols -- cgit v1.2.3