Fork of https://github.com/zephyrproject-rtos/Kconfiglib.git https://git.mcdonnell.dev/Kconfiglib.git/atom?h=v9.2.1 2018-07-20T20:09:51Z 2018-07-20T20:09:51Z Ulf Magnusson ulfalizer@gmail.com 2018-07-20T20:05:08Z urn:sha1:27173d98e5bdb714e10b233d4fa650927d8bcc03 Just adds commit 5452ad3 ("Fix detection of hex literals"). Braino. Include some int and hex literals in the Kstrict testcase too. 2018-07-20T19:34:25Z Ulf Magnusson ulfalizer@gmail.com 2018-07-20T19:34:25Z urn:sha1:52a099982ecb66eec1ae180f02fe58f2d9264078 Adds support for automatically warning for references to undefined Kconfig symbols. See commit ca89d02 ("Add KCONFIG_STRICT flag for flagging refs. to undefined syms"). (There was an outdated docstring in that comment. KCONFIG_STRICT needs to be set to "y".) 2018-07-20T19:32:24Z Ulf Magnusson ulfalizer@gmail.com 2018-07-20T19:31:00Z urn:sha1:ec57b1f3da0f0e2f348574a11a62b2c2c58cec42 Also fix up Kconfig.__init__() docstring to say that KCONFIG_STRICT needs to be "y". 2018-07-20T19:15:23Z Ulf Magnusson ulfalizer@gmail.com 2018-07-20T02:14:31Z urn:sha1:ca89d02ca1639b72c7b74834ff432ab10df58fe9 Settings KCONFIG_STRICT to y in the environment turns on warnings for all references to undefined symbols within Kconfig files (with the only gotcha that hex literals must be prefixed by 0x or 0X, to make it possible to distinguish them from undefined references). Always flagging undefined references gets awkward, as some projects (e.g. the Linux kernel) use multiple Kconfig trees with shared files, leading to some safe undefined references. It's helpful for other projects though. Having KCONFIG_STRICT as an environment variable is handy when multiple tools are involved. Piggyback a small README change re. warnings. Kconfiglib now has many more warnings than the C tools. 2018-07-18T13:18:37Z Ulf Magnusson ulfalizer@gmail.com 2018-07-18T13:18:37Z urn:sha1:17ae2520ba9de79e32bad3a005a9850568456d13 Adds e08b695 ("Add def_int, def_hex, and def_string keywords"), getting rid of some Kconfig inconsistency. 2018-07-18T01:23:43Z Ulf Magnusson ulfalizer@gmail.com 2018-07-18T01:05:37Z urn:sha1:e08b6957ca935fc97eddd1afda933715016b9b11 Analogous to def_bool and def_tristate, setting the type and adding a default at the same time. This is a Kconfiglib extension. These keywords can be useful in projects that make use of symbols defined in multiple locations, and remove some Kconfig inconsistency. 2018-07-15T15:37:52Z Ulf Magnusson ulfalizer@gmail.com 2018-07-15T15:37:52Z urn:sha1:f3ce3d5ddbf27400b22676409152213d9351216c 2018-07-15T14:46:47Z Ulf Magnusson ulfalizer@gmail.com 2018-07-15T14:46:47Z urn:sha1:bca625ae5d99872d8c1d21cbce6e407a8a4eaf6f This release revamps the globbing design to make 'source' globbing, requiring at least at least one matching file. A new o(r)source statement can be used when it's okay for a pattern to not match any files. Relevant commit, with motivations: 7a428aa ("Switch to more sensible globbing statements (w/ backwards compatibility)"). Backwards compatibility is maintained by having g(r)source be an alias for o(r)source. A small API change was introduced too: Kconfig.srctree is now set to the empty string instead of None when $srctree is unset. This gives nice behavior for e.g. os.path.join(). 2018-07-15T14:15:43Z Ulf Magnusson ulfalizer@gmail.com 2018-07-15T11:16:47Z urn:sha1:7a428aa415606820a44291f475248b08e3952c4b Instead of having 'source' and 'gsource', have 'source' always glob, but require the pattern to match at least one file, throwing KconfigError otherwise. Have separate 'osource' and 'orsource' statements (the o is for "optional") for cases where it's okay for the pattern to not match any files. This is analogous to 'include' and '-include' in Make. The biggest flaw with 'gsource' was that there was no way to do a globbing match while requiring something to match, possibly leading to subtle failures. Preserve backwards compatibility by having "gsource" and "grsource" be aliases for "osource" and "orsource", respectively. Also include some related changes: - Kconfig.srctree is now set to the empty string if $srctree is unset, rather than to None. This gives nice behavior with os.path.join() and os.path.relpath(), which treat the empty string as the current directory (without adding './', for os.path.join()). - When $srctree is set, Kconfig files in the current directory will no longer override Kconfig files in $srctree when the relative paths match. This was likely a bug all along in the C tools, and probably only makes sense for .config files. I've seen it cause breakage in Zephyr. - Clarify the behavior of $srctree in the Kconfig.__init__() docstring. - Make MenuNode.filename be relative to $srctree for the Kconfig file passed to Kconfig.__init__(). This makes it consistent. The major version will be bumped later due to the small Kconfig.srctree API change. 2018-07-13T17:00:28Z Ulf Magnusson ulfalizer@gmail.com 2018-07-13T17:00:28Z urn:sha1:e52afd688f1caa22ee722b971a2846083e4fbc2f This release adds commit ac692af ("Fix absolute $srctree prefixes showing up on gsource'd files"), which fixes a bug that could cause $srctree to be included in some paths for e.g. generated documentation.