Kconfiglib.git/tests, branch v6.0.1Fork of https://github.com/zephyrproject-rtos/Kconfiglib.githttps://git.mcdonnell.dev/Kconfiglib.git/atom?h=v6.0.12018-05-27T21:58:47ZProvide lists with all menus and comments2018-05-27T21:58:47ZUlf Magnussonulfalizer@gmail.com2018-05-27T21:58:47Zurn:sha1:fc73c461f1a8acf3e09670e8f9429c7ef9d0b71f
Handy e.g. when implementing advanced search features.
Micro-optimize _parse_help() loop2018-05-26T13:04:35ZUlf Magnussonulfalizer@gmail.com2018-05-26T12:53:28Zurn:sha1:ab2431ca36139c6d450adfe275d1e14088633eed
Shaves ~6% off the _parse_help() runtime for the x86 Kconfigs in
cProfile.
Record which MenuNode has each property2018-05-16T17:58:22ZUlf Magnussonulfalizer@gmail.com2018-05-14T12:48:22Zurn:sha1:63a44186137e2706afec0aef278cd5d123fc98dc
This allows accurate documentation to be generated for symbols and
choices defined in multiple locations. There are now MenuNode.defaults,
MenuNode.selects, etc., lists that mirror the corresponding
Symbol/Choice lists.
Symbol/Choice.__str__() now correctly show property locations as well,
by simply concatenating the strings returned by MenuNode.__str__() for
each node.
_parse_properties() was modified to add all properties directly to the
menu node instead of adding them to the contained symbol or choice. The
properties are then copied up to symbols and choices in
_finalize_tree(). Dependency propagation is handled at the same time.
As a side effect, this cleans up the code a bit and de-bloats
_parse_properties().
Update the menuconfig implementation to use the new functionality. It
now lists the menu nodes for symbols and choices with the correct
properties for each node (previously, all defaults, selects, implies,
and ranges appeared on the first definition).
Expand environment variables in strings directly2018-05-16T17:42:56ZUlf Magnussonulfalizer@gmail.com2018-05-14T16:00:40Zurn:sha1:cbf32e29a130d22bc734b7778e6304ac9df2a3e8
Make "$FOO" directly reference the environment variable $FOO in e.g.
'source' statements, instead of the symbol FOO. Use os.path.expandvars()
to expand strings (which preserves "$FOO" as-is if no environment
variable FOO exists).
This gets rid of the 'option env' "bounce" symbols, which are mostly
just spam and are buggy in the C tools (dependencies aren't always
respected, due to parsing and evaluation getting mixed up). The same
change will probably appear soon in the C tools as well.
Keep accepting 'option env' to preserve some backwards compatibility,
but ignore it when expanding strings. For compatibility with the C
tools, bounce symbols will need to be named the same as the environment
variables they reference (which is the case for the Linux kernel).
This is a compatibility break, so the major version will be bumped to 6
at the next release.
The main motivation for adding this now is to allow recording properties
on each MenuNode in a clean way. 'option env' symbols interact badly
with delayed dependency propagation.
Side note: I have a feeling that recording environment variable values
might be redundant to trigger rebuilds if sync_deps() is run at each
compile. It should detect all changes to symbol values due to
environment variables changing value.
Rename examples/menuconfig.py to menuconfig_example.py2018-04-30T23:28:44ZUlf Magnussonulfalizer@gmail.com2018-04-30T23:26:39Zurn:sha1:4d0d74dc0a10e63e1372f925d0d2493cba351aa1
To avoid confusing it with the new terminal menuconfig implementation.
Clean up the README a bit at the same time, removing some stuff that's
less essential now (e.g. the menuconfig_example.py "screenshot").
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.
Parenthesize && expressions within || expressions2018-03-28T18:29:20ZUlf Magnussonulfalizer@gmail.com2018-03-28T18:29:20Zurn:sha1:7245bad9ebb58fc8ce5a322081fc6c39d2dc59c6
This is redundant from an evaluation perspective, as && has higher
precedence than ||, but is easier to read.
A && B || C && D is now rendered as "(A && B) || (C && D)".
Refactor expr_str() cases2018-03-26T13:15:07ZUlf Magnussonulfalizer@gmail.com2018-03-26T13:12:09Zurn:sha1:6ef362c490bc2608c971eeabd5930ea0d8893dbe
- Detect Symbol directly instead of as (not tuple) + (not choice)
- Test explicitly for a tuple (non-Symbol) in NOT
- Add some tests to get better coverage for NOT and parentheses
Test grsource with nonexistent file2018-03-13T05:35:41ZUlf Magnussonulfalizer@gmail.com2018-03-13T05:32:47Zurn:sha1:044310b6398b4e0e914deda00509ad86febc521b
Just for completeness.
Add a globbing source statement2018-03-13T04:04:44ZUlf Magnussonulfalizer@gmail.com2018-03-13T02:24:41Zurn:sha1:daac69dc05217d024fbe021447629fa2b3d95b70
'gsource' works like 'source', but takes a glob pattern and sources all
matching files. Works as a no-op if no files match, and hence doubles as
an include-if-exists function, similar to '-include' in 'make'.
Add a 'grsource' statement as well, mirroring 'rsource'.
Came up in https://github.com/ulfalizer/Kconfiglib/pull/40.