Fork of https://github.com/zephyrproject-rtos/Kconfiglib.git https://git.mcdonnell.dev/Kconfiglib.git/atom?h=v9.4.1 2018-08-17T19:35:42Z 2018-08-17T19:35:42Z Ulf Magnusson ulfalizer@gmail.com 2018-08-17T19:04:43Z urn:sha1:8a3999bc708e8468ff79665e3cbdfccd603160e1 Due to a major design braino, the top-level Kconfig file passed to Kconfig.__init__() wasn't looked up relative to $srctree, breaking out-of-tree usage for e.g. menuconfig. With this change, Kconfig files are consistently looked up relative to $srctree, which makes a lot more sense. Also remove note re. loading a subset of Kconfig files. Saying that the top-level file and all source'd Kconfig files are looked up relative to $srctree should make the behavior clear enough. 2018-08-10T02:57:13Z Ulf Magnusson ulfalizer@gmail.com 2018-08-09T22:04:12Z urn:sha1:1f864b104a1f64b1c72ab13422070f6ad7cad225 Allow custom output formats for symbols/choices when turning expressions into strings, via a user-supplied callback function (sc_str_fn). This makes things like turning symbols into links in generated documentation and displaying symbol values in the menuconfig interface less hacky to implement. Two new Symbol/Choice.custom_str() functions were added, as passing extra arguments to __str__() is awkward. 2018-08-10T02:57:13Z Ulf Magnusson ulfalizer@gmail.com 2018-08-10T02:56:36Z urn:sha1:9f2c55dab1d966d5a759722b4939f1f2c30e5e5f Needs an initial rm_config() after earlier reorganization. 2018-07-20T20:09:51Z Ulf Magnusson ulfalizer@gmail.com 2018-07-20T20:03:43Z urn:sha1:2d391d8f369a40b438a1b246c888bb42b2e14278 Missing 'not'. Add some literals to the Kstrict testcase. 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-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-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-13T16:22:12Z Ulf Magnusson ulfalizer@gmail.com 2018-07-13T16:22:12Z urn:sha1:ac692af07a123b3d623e51df7f1e7a10b88c1ddd When using gsource with $srctree set to an absolute path, the $srctree prefix would show up in MenuNode.filename, trickling its way into e.g. generated documentation. This was due to a broken test: os.path.isabs() was checked after joining the pattern with $srctree, making it mistake an absolute $srctree for an absolute path in the Kconfig file. Fix the test. 2018-07-10T12:19:04Z Ulf Magnusson ulfalizer@gmail.com 2018-07-10T12:16:08Z urn:sha1:21b5351c3721359dbd28937c95e75ba4b435f0b7 Only out-of-range user values generated warnings before. The C tools warn for neither of them. 2018-07-10T05:56:37Z Ulf Magnusson ulfalizer@gmail.com 2018-07-03T16:30:06Z urn:sha1:2433deba7889931c4bae679f116887fe49a2ce04 Implement the Kconfig preprocessor described in https://github.com/torvalds/linux/blob/master/Documentation/kbuild/kconfig-macro-language.txt (which is now in linux-next and will appear in Linux 4.18). A new Kconfig.variables property holds all the preprocessor variables so that they can be inspected programmatically. Preprocessor variables are represented by a new Variable class. With the preprocessor, environment variables are referenced with $(FOO) instead of $FOO. For backwards compatibility, $FOO is accepted as well for now (and leaves "$FOO" as-is if FOO doesn't exist). The $FOO syntax might be dropped at some point in the future (together with a major version increase). It should be supported for a few months at least. Some internals were cleaned up too, mostly related to parsing. Some outdated documentation was fixed as well.