Fork of https://github.com/zephyrproject-rtos/Kconfiglib.git https://git.mcdonnell.dev/Kconfiglib.git/atom?h=v10.36.0 2019-01-15T22:12:10Z 2019-01-15T22:12:10Z Ulf Magnusson ulfalizer@gmail.com 2019-01-15T22:11:34Z urn:sha1:770abd61a5c90837d9336afd972090eebbc26b0b 2018-11-23T09:29:57Z Ulf Magnusson ulfalizer@gmail.com 2018-11-23T00:33:32Z urn:sha1:ab89ef6aa7b8fef0eb410949c86a25e55586a972 These are pretty hot. Inline them to save a few % of parsing time. They're pretty simple anyway. _tokens_i was initialized to -1 to simplify the _next_token() implementation. With _next_token() gone, initialize it to 0 instead, which simplifies some other code. 2018-11-21T10:34:32Z Ulf Magnusson ulfalizer@gmail.com 2018-11-21T10:17:28Z urn:sha1:01757e5ac9324948ca64a4cf512352b09956a8fa The KCONFIG_WARN_UNDEF test often fails on Python 3.4 (3.5 not tested), but the output is still correct. It just differs due to dict ordering randomness. Python 3.6 iterates over dicts in insertion order in practice, and Python 3.7 made it part of the spec, so enable the test for 3.6 and later. Python 2.7 seems fine as well. 2018-11-06T10:48:42Z Ulf Magnusson ulfalizer@gmail.com 2018-11-06T10:16:28Z urn:sha1:7992519be5d59a69dc71f43ec2f34c5594afdb14 Previously, you could get either one or two newlines at the end of MenuNode.help and the various __str__() methods, though this wasn't documented. Always stripping trailing whitespace is cleaner e.g. when using print(), which automatically appends a trailing newline, and makes things consistent. Hopefully nothing relied on the old undocumented behavior. It's fine for genrest.py at least. 2018-11-02T02:52:46Z Ulf Magnusson ulfalizer@gmail.com 2018-11-02T01:35:49Z urn:sha1:0e6cd82908f5c649e15e6a63ad77a94f627449d2 Despite 'if' nodes being flattened before 'if' removal, consecutive 'if' nodes can still show up for code like the following: ... if X endif if X endif ... _remove_ifs() failed to remove the second 'if' node, leading to a crash e.g. when turning on show-all mode in the menuconfig in a menu with such code (due to the unexpected 'if' node). Stuff like the above could potentially result from 'osource's with no matches, though I just spotted the error while looking over the code. Fix the 'if' removal logic to properly handle consecutive 'if' nodes. 2018-10-26T21:34:18Z Ulf Magnusson ulfalizer@gmail.com 2018-10-26T20:23:27Z urn:sha1:699fd81bf3a67606396035697357c5665dcd68af This makes it possible to enable it for the bundled tools, by setting KCONFIG_WARN_UNDEF_ASSIGN=y. Previously, the code had to be modified to call Kconfig.enable_undef_warnings(). Also rename KCONFIG_STRICT to KCONFIG_WARN_UNDEF, for consistency. Keep supporting KCONFIG_STRICT as an alias for backwards compatibility. 2018-10-21T15:28:31Z Ulf Magnusson ulfalizer@gmail.com 2018-10-21T14:09:24Z urn:sha1:9a4127a1d5eeac122cb478b0e03d42c9698c41be Add a Variable.expanded_value_w_args() function for expanding a preprocessor function with particular arguments. This is what expanded_value should have been, because expanded_value_w_args() is more general (expanded_value corresponds to zero arguments). Keep expanded_value for backwards compatibility though. Also add a simple __repr__() to Variable. It could show the expanded value, but that might mean calling shell functions or user-defined functions as a side effect (possibly with missing arguments). Not sure that's a good idea, so just show the unexpanded value. 2018-10-16T05:35:53Z Ulf Magnusson ulfalizer@gmail.com 2018-10-16T04:58:54Z urn:sha1:98af94da6a9ef81c8e2c56fbf60741fa8d2a2dd1 Kconfig.choices has accidentally been identical to Kconfig.unique_choices all along, because named choices defined in multiple locations (which are pretty obscure) were only added once. Fix Kconfig.choices to match its description. This simplifies the code a bit too. Kconfig.unique_choices is usually what you want. 2018-09-29T16:08:52Z Ulf Magnusson ulfalizer@gmail.com 2018-09-29T14:27:21Z urn:sha1:c1dcaa3ccbb263f021157f2aebd185c6388c28a1 Handle the line-after-help-text case specially, which allows _has_tokens (renamed to _reuse_tokens) to be used as the unget mechanism for help texts as well, leaving _saved_line unused. Move the _reuse_tokens check into _next_line(). This makes _parse_block() as straightforward as _parse_properties(), and simplifies _parse_properties() a tiny bit too by getting rid of the '_tokens_i = -1' assignment. 2018-09-23T15:31:20Z Ulf Magnusson ulfalizer@gmail.com 2018-09-20T11:33:59Z urn:sha1:6156041560c75831e003202b790ab3f435bbb388 Allow preprocessor functions to be defined in Python by putting a module called 'kconfigfunctions' into sys.path. Internally, this simply adds the functions to the predefined functions in Kconfig._functions. User-defined Python functions make it simple to integrate information from existing Python tools into Kconfig, e.g. to have Kconfig symbols depend on hardware information stored in some other format. This might be used to get device tree information into Kconfig in Zephyr. Piggyback module docstring documentation for some extensions that were previously only mentioned in the README.