Kconfiglib.git/kconfiglib.py, branch v5.0.0Fork of https://github.com/zephyrproject-rtos/Kconfiglib.githttps://git.mcdonnell.dev/Kconfiglib.git/atom?h=v5.0.02018-05-01T05:53:08ZMake warnings available in a list2018-05-01T05:53:08ZUlf Magnussonulfalizer@gmail.com2018-05-01T04:33:32Zurn:sha1:ed3ceaa05626fb62f50508843fdbf738bf6c2c64
Also make printing of warnings to stderr optional. It's on by default,
since it's almost always what you want.
This makes printing and processing of warnings more flexible, compared
to always printing warnings to stderr as soon as they're generated. It
was inspired by wanting to promote certain warnings to errors in Zephyr,
which previously required capturing stderr.
Make disable_warnings() disable all warnings2018-05-01T04:22:12ZUlf Magnussonulfalizer@gmail.com2018-05-01T03:10:40Zurn:sha1:8983f7eb297dd614faf0beee3129559bc8ba338e
...including the optional ones. Previously, those were independent.
This is more intuitive, and it seems unlikely that you'd want some of
the optional warnings printed without having general warnings printed.
This is a small API behavior change, so the major version will be bumped
to 5 at the next release. Programs that enabled optional warnings
without enabling general warnings will be affected.
This means that all warnings now go through the same code path, which
will come in handy for later changes (making the warnings available in a
list, though with stderr printing still enabled by default).
Add some more documentation for the Kconfig.__init__() 'warn' parameter
and the enable_redun_warnings() function as well, and clean up the
variable naming a bit.
Give filename and context for UnicodeDecodeError2018-04-25T18:26:39ZUlf Magnussonulfalizer@gmail.com2018-04-25T18:19:17Zurn:sha1:09b8c589681b1141e7b36a6e487c953c7e6e3c18
These errors are a pain to debug otherwise, and might look like
Kconfiglib brokenness.
Another option would be ignore decoding errors, or do the
'surrogateescape' thing on reading and writing, but keep it simple for
now. Pointing out the problem might be more helpful.
Print a warning for malformed .config lines2018-04-25T12:41:21ZUlf Magnussonulfalizer@gmail.com2018-04-25T12:30:25Zurn:sha1:c1c5ef2eb1009bacb6f7278e7d73335ec6223cba
Flag lines matching neither 'CONFIG_FOO=...' nor
'# CONFIG_FOO is not set' that aren't blank or comments.
Add Choice.direct_dep field2018-04-19T06:38:44ZUlf Magnussonulfalizer@gmail.com2018-04-19T06:29:59Zurn:sha1:509e374dfcadbe04ba30fe8aeea372101e0b5502
Same as Symbol.direct_dep (OR of node dependencies from all definition
locations). It's handy to have available when generating information
about choices.
Add helper for splitting expressions2018-04-11T19:40:14ZUlf Magnussonulfalizer@gmail.com2018-04-11T18:35:40Zurn:sha1:105c835e70a5bb80a256b3d10d1d03dee7bb23db
I've had to implement the logic for walking reverse dependencies (from
select) a couple of times now, and it's always a bit tricky to get
right. Reduce code duplication and simplify things by adding a helper
function split_expr() that splits an expression into a list of either
its AND or OR operands.
A nice side effect is that e.g. the warning generated for selecting a
symbol with unsatisfied direct dependencies now lists the selecting
symbols in the order that they appear in the Kconfig files.
split_expr() might be helpful for splitting other types of expressions
as well, e.g. to put operands on separate lines when generating
documentation.
Move sanity checking to after _finalize_tree()2018-04-06T14:59:24ZUlf Magnussonulfalizer@gmail.com2018-04-06T14:41:01Zurn:sha1:e8408a06c68d87485a9d45817dfdd60e722a6f1c
Previously, the warnings
warning: FOO (defined at Kconfig:1, Kconfig:6) defined with type unknown
warning: the default selection BAR (defined at Kconfig:9) of FOO (defined at Kconfig:1, Kconfig:6) is not contained in the choice
were printed for this (obscure, but okay) pair of definitions:
choice FOO
default BAR
endchoice
choice FOO
prompt "foo"
config BAR
bool "bar"
endchoice
The problem is that BAR is not known to be a choice symbol by the time
the first choice definition is encountered in _finalize_tree(), since
that's determined only when the second definition is encountered (it
needs to happen there, because implicit submenus can influence whether a
symbol is a choice symbol or not, and implicit submenus are determined
in _finalize_tree()).
Fix it by moving the sanity checks out of _finalize_tree() and into a
separate pass over all symbols and choices that runs after
_finalize_tree(). That might avoid other gotchas too.
Set is_menuconfig True on the top menu2018-04-05T07:03:15ZUlf Magnussonulfalizer@gmail.com2018-04-05T07:00:04Zurn:sha1:981d24aff765794f4ab440f29b1543a118222357
Oversight
Code consistency nit2018-04-04T15:30:02ZUlf Magnussonulfalizer@gmail.com2018-04-04T15:29:34Zurn:sha1:9c86dfd60273dc894da1db89220aff8d4de4716e
'is_menuconfig' is set after 'item' in the other cases.
Generalize is_menuconfig to non-symbol items2018-04-04T14:44:58ZUlf Magnussonulfalizer@gmail.com2018-04-04T14:20:58Zurn:sha1:2259d353426f12d5fa807075fb4727e64331ac8a
Extending the scope of is_menuconfig so that it's True for all items
whose children should be displayed in a separate menu turns out to be
handy when implementing menuconfig-like functionality.
Keep the old name for backwards compatibility. It's good enough.