Fork of https://github.com/zephyrproject-rtos/Kconfiglib.git https://git.mcdonnell.dev/Kconfiglib.git/atom?h=v10.8.0 2018-09-23T15:31:20Z 2018-09-23T15:31:20Z Ulf Magnusson ulfalizer@gmail.com 2018-09-23T15:02:29Z urn:sha1:8643ee72df15037ad8af6ce62c85880dc357eb9c Adds support for user-defined preprocessor functions in Python, which can be used to get information from existing Python tools into Kconfig, e.g. to have Kconfig symbols depend on hardware information stored in some other format. See commit b6827ca ("Add support for user-defined Python preprocessor functions"). 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-19T05:28:47Z Ulf Magnusson ulfalizer@gmail.com 2018-09-19T05:22:06Z urn:sha1:3df532b8d4cdf6915eaf079ee8082f792ab9b0cb - Remove some unused imports - Replace a lambda with a plain function - Shorten some long lines - Remove some redundant backslashes within brackets 2018-09-19T03:53:31Z Ulf Magnusson ulfalizer@gmail.com 2018-09-19T03:47:47Z urn:sha1:f832115f1431fb3cee06cfb19095923096c1a0ae Also remove some redundant backslashes within brackets. 2018-09-15T01:07:11Z Ulf Magnusson ulfalizer@gmail.com 2018-09-15T00:19:34Z urn:sha1:35a60b786c646c846d9bad6a5f15711acc9a62c6 Simplifies the code. Should promote new APIs. Also fix list_undefined.py for recent kernels. More environment variables are referenced now. 2018-09-14T20:14:43Z Ulf Magnusson ulfalizer@gmail.com 2018-09-14T20:14:43Z urn:sha1:f861c271dcbb06e0101c01add3d07006c2d3a09c No idea where "menu." came from. 2018-09-14T19:37:14Z Ulf Magnusson ulfalizer@gmail.com 2018-09-14T19:37:14Z urn:sha1:5f1e821ceee9771a306e40704f22dc63d1dd6836 Adds commit b9b2ebb ("menuconfig: Add RGB color support to styles."), which makes it possible to specify colors in MENUCONFIG_STYLE using #RRGGBB notation. The rendered colors may be more or less exact depending on terminal capabilities. In the best case, we can redefine colors. Otherwise, we fall back on the closest available color. Contributed by Mitja Horvat (punkfluid). 2018-09-14T19:18:49Z Ulf Magnusson ulfalizer@gmail.com 2018-09-14T19:04:23Z urn:sha1:325431ae3261420ff8e852c39ad9d116f2b40616 - Point out where the styling part starts and ends - Move _style_attr() into the styling part (by moving the comment) - Move _name_and_val_str() and _expr_str() to later in the file, closer to where they're used (mostly in the help dialog) - Turn _input_dialog() input handling into one if-elif-... chain, like for the other dialogs. 2018-09-14T18:57:00Z Ulf Magnusson ulfalizer@gmail.com 2018-09-14T18:42:24Z urn:sha1:8e889e06bd1312611afb1cb9642d16fe0587970f Prevent the 'Symbol/choice/menu/comment information' title string from disappearing when it won't fit on the terminal. Piggyback some code nits: - Remove a redundant 'global _style' - Use 'elif' after checking for KEY_RESIZE - Consistently use '_sel_node_i = _menu_scroll = 0' to reset positions, e.g. when entering menus 2018-09-14T08:33:37Z Ulf Magnusson ulfalizer@gmail.com 2018-09-14T04:03:33Z urn:sha1:7762405a3ae5e8e107d24b4c64215aaaa5a04c50 - Make the coding style a bit more consistent with the rest of the code - Allow colors to be allocated from the xterm 256-color grayscale range, and emulate it when dynamically allocating colors. Never allocate above color number 255 though, as anything there would be unknown territory. - Switch back to consistently passing tuples to functions. This was the original design, before I suggested changing it... - Remove some repeated information from docstrings and fix some small typos - Make use of the element1=element2 feature in the style definition for the 'default' style