Fork of https://github.com/zephyrproject-rtos/Kconfiglib.git https://git.mcdonnell.dev/Kconfiglib.git/atom?h=v10.32.0 2018-12-08T02:28:52Z 2018-12-08T02:28:52Z Ulf Magnusson ulfalizer@gmail.com 2018-12-07T23:41:01Z urn:sha1:7b4f72fa7a19b7c38312a6f6fd553ca45f04e9a6 Make the previously obligatory 'filename' argument to load_config() and write_config() default to None, and have that implement the behavior you'd usually want: read/write either KCONFIG_CONFIG or ".config" if unset, and read the 'option defconfig_list' configuration file if KCONFIG_CONFIG/".config" doesn't exist. For load_config(), filename=None also allows the configuration file to be missing without raising an error. load_config() returns True if a local configuration file was loaded, which is useful to check in the menuconfig (if no local configuration file exists, we always want to prompt for saving the configuration when exiting). Also add a 'verbose' argument (default True) to load_config() and read_config() that makes them print which files were read/written in filename=None mode. Also generalize olddefconfig.py and oldconfig.py to not require there to already be a local configuration file. This was a bit silly for olddefconfig.py in particular. Remove the examples/defconfig.py script. It's a duplicate of olddefconfig.py. 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-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-23T18:22:30Z Ulf Magnusson ulfalizer@gmail.com 2018-09-23T18:20:49Z urn:sha1:a3f37faed0aaa024fa6354a429ace427a6dc807c 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. 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.