Fork of https://github.com/zephyrproject-rtos/Kconfiglib.git https://git.mcdonnell.dev/Kconfiglib.git/atom?h=v10.7.0 2018-09-04T18:49:21Z 2018-09-04T18:49:21Z Ulf Magnusson ulfalizer@gmail.com 2018-09-04T16:05:28Z urn:sha1:a092257a49ed7850913cf53e474f4c8dd175c94b The C implementation supports this (though it's undocumented, and unused to far). This can be used e.g. to dynamically instatiate symbols from template files: Kconfig.template: config $(subsys)_LOG bool "Enable logging for $(subsys)" depends on $(subsys)_HAS_LOG ... other stuff dependent on $(subsys) Elsewhere: subsys = FOO source "Kconfig.template" subsys = BAR source "Kconfig.template" Pretty sure this can easily be abused, but it should be supported at least. 2018-08-25T18:32:34Z Ulf Magnusson ulfalizer@gmail.com 2018-08-25T18:07:05Z urn:sha1:932d0f7b8a69bdcac5d945de600ce6be807aeff7 Kconfig.env_vars is a set() with the names of all environment variables referenced in the configuration. Can be used e.g. for custom incremental build implementations, though sync_deps() already indirectly catches any relevant changes to environment variables. 2018-08-23T23:01:36Z Ulf Magnusson ulfalizer@gmail.com 2018-08-23T00:43:00Z urn:sha1:13884e934ec8eda928234c6506ae27f0334ec31b Add a MenuNode.include_path attribute that holds a tuple of (filename, linenr) tuples, giving the locations of the 'source' statements via which the node's Kconfig file was included, starting from the top-level Kconfig file. Use MenuNode.include_path to give the include path for symbols and other items in the help display in the menuconfig interface. This is useful for figuring out how Kconfig files are organized, and when reorganizing things. 2018-08-23T09:42:49Z Ulf Magnusson ulfalizer@gmail.com 2018-08-23T08:45:42Z urn:sha1:3aca83eaf20f5e278b6d260cb255e6a9385590db The recursive 'source' detection was still fine, but the error reporting had broken due a missed variable renaming. The test suite didn't catch it, because a different type of KconfigError was raised instead, due to a separate error in the test suite (need to include tests/Krecursive{1,2}, since paths are relative to $srctree). Fix the variable name and tighten up the tests to check that the KconfigError message is the one we except. Tighten up the dependency loop detection tests in the same way too. 2018-08-21T13:19:52Z Ulf Magnusson ulfalizer@gmail.com 2018-08-21T12:08:55Z urn:sha1:d78c293c41351256f76fb2fa27e72e399b130e4f I accidentally broke this when I added the _defined_syms_set optimization. No semantic difference, but having the order match is more readable. 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-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.