Fork of https://github.com/zephyrproject-rtos/Kconfiglib.git https://git.mcdonnell.dev/Kconfiglib.git/atom?h=v13.6.0 2019-12-14T17:28:22Z 2019-12-14T17:28:22Z Ulf Magnusson ulfalizer@gmail.com 2019-12-14T17:25:18Z urn:sha1:2e08499ce38ca7bf2f368c4dc321ef8a6f287530 Tweak messages and variable names to match. 2019-12-14T17:12:07Z Ulf Magnusson ulfalizer@gmail.com 2019-12-14T17:04:09Z urn:sha1:1ec91703ecdb4c369212fabe2ca0a68f040b7697 Tools that don't use standard_kconfig() currently generate spammy tracebacks for e.g. syntax errors. Add a suppress_traceback flag to Kconfig.__init__() for catching "expected" exceptions and printing them to stderr and exiting with status 1. Use it to make all tools consistently hide tracebacks. 2019-11-20T18:40:00Z Ulf Magnusson ulfalizer@gmail.com 2019-11-20T18:38:02Z urn:sha1:810ae682a3b80ed621fd1e20c01241ac48381156 Handy for KCONFIG_{CONFIG,AUTOHEADER}_HEADER. 2019-11-17T05:03:00Z Ulf Magnusson ulfalizer@gmail.com 2019-11-17T04:39:37Z urn:sha1:bb3be6ee9793f23c275d318f58cb6cf21391b371 This environment variable is used by the C tools. Use it when filename=None is passed to write_autoconf(), and default to include/generated/autoconf.h for compatibility. Also update genconfig.py to use KCONFIG_AUTOHEADER if set when no --header-path is passed. If KCONFIG_AUTOHEADER isn't set, keep defaulting to 'config.h' for backwards compatibility. It's probably a saner default for tools as well. 2019-11-17T04:32:59Z Ulf Magnusson ulfalizer@gmail.com 2019-11-17T02:41:12Z urn:sha1:de45874719772a40f1d8d244e2f5a6c6036415ac If no header string is specified in write_(min_)config() or write_autoconf(), use the values of the environment variables KCONFIG_CONFIG_HEADER and KCONFIG_AUTOHEADER_HEADER, respectively, if set. KCONFIG_AUTOHEADER_HEADER is consistent with KCONFIG_AUTOHEADER (the header path), which will be added soon. Using environment variables avoids having to add separate flags to each tool that writes configuration files or headers. Like for $prefix and $CONFIG_, store the values of the environment variables when the Kconfig instance is created, and expose them via Kconfig.config_header and Kconfig.header_header. This if flexible and avoids gotchas when working with multiple Kconfig instances. Also remove the old default header and make the default no header. Less advertising, but it felt a bit silly to add workarounds to keep it. Came up in https://github.com/ulfalizer/Kconfiglib/pull/80. 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