Fork of https://github.com/zephyrproject-rtos/Kconfiglib.git https://git.mcdonnell.dev/Kconfiglib.git/atom?h=v12.11.0 2019-06-07T05:29:38Z 2019-06-07T05:29:38Z Ulf Magnusson ulfalizer@gmail.com 2019-06-07T05:29:38Z urn:sha1:929a5981c717d2e72e4b181b1a81d0b181d6b411 Match the order the flags are defined. 2019-06-07T05:03:17Z Ulf Magnusson ulfalizer@gmail.com 2019-06-06T17:08:34Z urn:sha1:dd1be546016b227411e50376515956ed381ee270 This can be useful to avoid needless reconfiguration, by checking if any Kconfig file or environment variable has changed value before running genconfig. 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-05-30T22:08:14Z Ulf Magnusson ulfalizer@gmail.com 2019-05-29T05:29:20Z urn:sha1:175c1f5a363e51a76a7dc1fe807f7c3faf40ab23 Before writing a configuration file or header file, compare the old contents of the file against the new contents. If there's no change, skip the write, to avoid updating the file modification time. This might avoid triggering redundant rebuilds depending on how the build system is set up, and could allow for a simpler setup. 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-03-06T00:55:57Z Ulf Magnusson ulfalizer@gmail.com 2019-03-06T00:55:57Z urn:sha1:b07c2053de324d974521c83e7a073ff1330b74d8 Used in a single place. 2019-01-15T22:12:10Z Ulf Magnusson ulfalizer@gmail.com 2019-01-15T22:11:34Z urn:sha1:770abd61a5c90837d9336afd972090eebbc26b0b 2018-12-08T13:44:27Z Ulf Magnusson ulfalizer@gmail.com 2018-12-08T13:44:27Z urn:sha1:e8f9751218fe8995d17c8c809e23d965df08d6ec Configuration files generated by --config-out would usually be an internal detail of the build system, so it's probably not helpful to generate *.old files for them. Pass save_old=False to write_config() to skip it.