Kconfiglib.git, branch v10.6.0Fork of https://github.com/zephyrproject-rtos/Kconfiglib.githttps://git.mcdonnell.dev/Kconfiglib.git/atom?h=v10.6.02018-09-08T00:03:52ZMake 10.6.0 release2018-09-08T00:03:52ZUlf Magnussonulfalizer@gmail.com2018-09-08T00:03:52Zurn:sha1:9b87ad921b5d95cbc002714d1ce4b98249811856
New features:
- Commit ac8d152 ("menuconfig: Add support for custom color schemes
(aka styles)"), contributed by Mitja Horvat (pinkfluid), adds support
for configuring the style (colors and attributes) of menuconfig
interface elements by setting a new MENUCONFIG_STYLE environment
variable.
The format of MENUCONFIG_STYLE is documented in the menuconfig.py
module docstring. This format is now used internally as well to
define the predefined styles.
- Commit a092257 ("Allow macro expansion within symbol names") adds
support for expanding macros within symbol names. This could be used
e.g. to define template Kconfig files that get instantiated by
setting preprocessor variables before including them.
Other changes:
- Commit 6683213 ("Allow user values on 'option env' symbols") makes it
possible to give 'option env' symbols user values. There's no good
reason to disallow it (it's a leftover from an older way of
implementing them), and it simplifies the code a bit.
Note that 'option env' symbols are only supported for backwards
compatibility at this point. Environment variables can be expanded
directly.
menuconfig: Pass a style string to _styled_win()2018-09-07T23:57:59ZUlf Magnussonulfalizer@gmail.com2018-09-07T23:55:10Zurn:sha1:2a1acdd37cdcd8590e0d1f3eccc314bdd501a443
Enforces that all windows are created from styles defined via the new
styling mechanism.
menuconfig: Print warnings instead of having StyleError2018-09-07T23:38:24ZUlf Magnussonulfalizer@gmail.com2018-09-07T23:30:56Zurn:sha1:4e25d1c713b0c37feb6a8781a92b62a52ee5eb04
Mostly motivated by curses.COLORS, which depends on the terminal.
It's probably friendlier to run even if the style gets a bit messed up,
but it's also nice to point out problems.
Missing style templates and missing styles to the left of '=' are
pointed out now too, with the help of some flag hackery.
Prefix the warnings with 'menuconfig warning:' to make it easier to
distinguish them from warnings from Kconfiglib.
menuconfig: Ignore non-existent style templates2018-09-07T22:00:16ZUlf Magnussonulfalizer@gmail.com2018-09-07T21:58:38Zurn:sha1:1f16f10dab298a121f8ff709312f694dc4b86354
This is consistent with non-existent styles being ignored, and gives
some forwards/backwards compatibility.
I wonder if there should be a warning for both instead.
Piggyback some nits.
menuconfig: Fix off-by-one in range check for COLORS2018-09-07T21:40:10ZUlf Magnussonulfalizer@gmail.com2018-09-07T21:34:43Zurn:sha1:df04a0c8fb020773e4708d00ee061e8f7a0501b9
"color values are expected to be in the range 0 to COLORS-1", from
init_color(3ncurses).
menuconfig: Allow numbers to be used directly for colors2018-09-07T21:24:40ZUlf Magnussonulfalizer@gmail.com2018-09-07T19:38:58Zurn:sha1:0bb65bc5628c7493897bf2f8cc786bcbbbcdefe5
Make the syntax 'fg:123' instead of 'fg:color123'. This is a bit easier
to type. Hex and octal constants are accepted as well.
menuconfig: Add support for custom color schemes (aka styles)2018-09-07T19:11:43ZMitja HORVATpinkfluid@gmail.com2018-08-29T20:53:49Zurn:sha1:ac8d152ec81a82ebacb0e77c3aa6f0cd81638f80
- introduce the _parse_styles() function which can take a string
defintion and parse it into a color structure that can be used
by UI elements
- the _parse_styles() function modifies a global dictionary (_style)
which is subsequentially used to style the UI elements
- the _style_to_curses() function takes a string representation
of style colors and converts it to ncurses attributes.
For eaxmple: fg:brightred,bg:black,bold -> returns a color
pair representing brightred and black ORed with A_BOLD
- simplify _init_styles() as now the majority of the heavy lifting
is done by _parse_styles(). _init_styles() initializes the
default theme (either "defualt" or "monochrome")
- terminals without color capabilities are now handled by using
the "monochrome" theme. This theme doesn't use any colors
but rather just bold and standout attribtes.
- add support for the "underline" attribute
- add doctstring at the beginning describing the style syntax
- rename the _style() function to _style_attr() as it was conflicting
with the global _style dictionary
- introduce the StyleError exception; this one is thrown if an error
in the style syntax is encountered
Clean up _expand_name() comments2018-09-05T10:19:39ZUlf Magnussonulfalizer@gmail.com2018-09-05T10:18:26Zurn:sha1:2be02fac785272e3bcea2cef619954535dc9abe0
Some grammar, some copy-paste errors ('string' should be 'name').
Fix outdated comment re. $() yielding non-const symbols2018-09-04T19:35:16ZUlf Magnussonulfalizer@gmail.com2018-09-04T19:35:16Zurn:sha1:0591946c28107001f4c5ca725405b8c2270be0dd
This is handled earlier in _tokenize() now.
Allow macro expansion within symbol names2018-09-04T18:49:21ZUlf Magnussonulfalizer@gmail.com2018-09-04T16:05:28Zurn: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.