Fork of https://github.com/zephyrproject-rtos/Kconfiglib.git https://git.mcdonnell.dev/Kconfiglib.git/atom?h=v12.12.1 2019-06-03T04:50:06Z 2019-06-03T04:50:06Z Ulf Magnusson ulfalizer@gmail.com 2019-06-02T23:55:50Z urn:sha1:bf36f5de0f49d56975b1a844e25484ec385dc971 A wart of the warning control API (enable/disable_*_warnings()) is that the current warning settings can't be queried. Querying warning settings is useful in functions that want to temporarily enable/disable some warning and then put things back to how they were. kconfiglib.load_allconfig() ran into this, for example. Make the internal warning control variables public (improve the naming at the same time), and encourage just setting them directly. Keep the old API for backwards compatibility. Also remove _warn_redun_assign() and _warn_override(). They're trivial and were called in a single place. 2019-06-03T04:50:06Z Ulf Magnusson ulfalizer@gmail.com 2019-06-02T16:15:59Z urn:sha1:55bc8c380869ea663092212e8fe388ad7abae596 Hardcoding load_config() and write_(min_)config() to write any message to stdout is awkward, because it means that the message can't be easily reused when stdout is the wrong place to write it to (e.g. in menuconfig/guiconfig). This gets extra bad now that there's also the "No change to ..." message. Modify load_config() and write_(min_)config() to return the message as a string instead, and have them always return a message, instead of just when 'filename' is None and verbose=True. This makes things flexible and straightforward. Use the new behavior in menuconfig.py and guiconfig.py. They now show "No change to ..." when saving a file doesn't modify it. Tools that want to write messages to stdout should now do print(kconf.load_config()) / print(kconf.write_config()). There's no clean way to preserve perfect backwards compatibility here, but keep accepting the 'verbose' argument and print a deprecation warning if a value is ever passed for it. That way, scripts will keep running, though possibly with less output on stdout. This changes the meaning of the load_config() return value as well, though I suspect it was only ever used by the menuconfig/guiconfig interfaces. The new behavior applies for kconfiglib.VERSION >= (12, 0, 0). 2019-03-22T19:43:30Z Ulf Magnusson ulfalizer@gmail.com 2019-03-22T19:43:21Z urn:sha1:5cec7cc7ecc78e8fe52c715c7465b0256392f428 2019-03-22T16:29:12Z Ulf Magnusson ulfalizer@gmail.com 2019-03-22T14:42:45Z urn:sha1:c70a45eb935dc536ce59ec860c17b4c1c531a663 This makes running pydoc(3) on the utilities helpful. Reuse the module docstring for the --help text for utilities that use argparse. Also fix some copy-paste errors in the all*config.py descriptions and clean up the language a bit. Piggyback removal of an optimization in allmodconfig.py that's pretty irrelevant now. 2019-03-06T01:03:41Z Ulf Magnusson ulfalizer@gmail.com 2019-03-06T00:58:06Z urn:sha1:553cca8e7417ad863b923758e6d402296d05de9c Also remove some no longer used imports. 2019-01-15T22:12:10Z Ulf Magnusson ulfalizer@gmail.com 2019-01-15T22:11:34Z urn:sha1:770abd61a5c90837d9336afd972090eebbc26b0b 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-17T18:03:36Z Ulf Magnusson ulfalizer@gmail.com 2018-11-17T08:21:13Z urn:sha1:b65baa47f69ae4c3993876a7edf0da0075aa70ff This allows some symbol values to be forced while running all{def,no,yes,mod}config.py. See Documentation/kbuild/kconfig.txt in the Linux kernel. Add a helper function load_allconfig() to Kconfiglib to avoid code duplication in the tools. Also add functions for enabling/disabling the warning that's generated when a symbol is assigned multiple times in a (set of) .config files and the values differ. It should be disabled when merging the KCONFIG_ALLCONFIG configuration file. Previously, only the warning generated when the assigned values are identical could be disabled. Disable all warnings related to assigning a symbol multiple times in examples/merge_config.py as well. 2018-08-22T18:05:11Z Ulf Magnusson ulfalizer@gmail.com 2018-08-22T00:25:20Z urn:sha1:d2c1430c91c574dc0dfd84f3652c8d9af8c77568 These are the same as Kconfig.defined_syms and Kconfig.choices, except duplicates are removed. Kconfig order is still preserved. This is almost always what you want when iterating through symbols and choices, as it potentially saves work, avoids generating duplicates when writing output, and still preserves Kconfig order for readability. The old attributes will be kept for backwards compatibility (maybe there's some rare cases where they could be useful too). They're created internally anyway. 2018-07-11T12:55:25Z Ulf Magnusson ulfalizer@gmail.com 2018-07-11T08:25:41Z urn:sha1:71872a88641f713dfa986906e860c320a74fd84a U-Boot has a ton of definition locations for some symbols, causing a lot of redundant work when iterating over Kconfig.defined_syms in _build_dep(). Iterate over set(Kconfig.defined_syms) instead, wherever possible. This speeds up the U-Boot parsing time from 4 seconds to 0.6 seconds on my machine. Also update the bundled tools to iterate over set(Kconfig.defined_syms). The performance loss is negligible even for projects that don't use multiple definition locations. Update the documentation to clarify that symbols/choices defined in multiple locations appear multiple times in Kconfig.defined_syms/choices as well.