Kconfiglib.git, branch v13.2.0Fork of https://github.com/zephyrproject-rtos/Kconfiglib.githttps://git.mcdonnell.dev/Kconfiglib.git/atom?h=v13.2.02019-10-29T18:08:54ZMake 13.2.0 release with Symbol/Choice.name_and_loc helper2019-10-29T18:08:54ZUlf Magnussonulfalizer@gmail.com2019-10-29T17:38:40Zurn:sha1:faa1d2199801a19d7eef3caba8f0519a224ada2f
Adds a helper that's handy for messages involving symbols/choices, and a
small documentation fix.
- Commit e1ccf19 ("Add public helpers for generating "<name> (defined
at ...)" strings").
- Commit 2d1cb7e ("Add missing Choice.str_value documentation")
Add public helpers for generating "<name> (defined at ...)" strings2019-10-29T17:30:46ZUlf Magnussonulfalizer@gmail.com2019-10-29T15:41:03Zurn:sha1:e1ccf19f9f5fc896dfeef15883d2cb455cbbb937
Have Symbol/Choice.name_and_loc return strings like
"MY_SYM (defined at foo:1, bar:2)"
"<choice> (defined at foo:4)"
I've added a function like that in at least four different scripts now,
so that's probably a sign that it's a worthwhile helper.
Clean up the tests/Klocation tests a bit while adding tests.
Add missing Choice.str_value documentation2019-10-29T15:28:54ZUlf Magnussonulfalizer@gmail.com2019-10-29T15:24:01Zurn:sha1:2d1cb7eae230a560e02b7a8bdee2cf0526d169e2
Oversight. It's just a string version of Choice.tri_value, like for
Symbol.tri_value vs. Symbol.str_value.
Also rearrange the property documentation to put user_value next to
tri_value and str_value in the Symbol and Choice docstrings.
Link RST versions of Kconfig documentation2019-10-10T11:35:57ZUlf Magnussonulfalizer@gmail.com2019-10-10T11:34:25Zurn:sha1:845f9d24972ff5e4a4d63f995dcedbd029821c74
The Linux docs were updated from plain text to RST.
Make 13.1.1 release2019-10-10T09:59:49ZUlf Magnussonulfalizer@gmail.com2019-10-10T09:59:01Zurn:sha1:bf01114a0ce09b891ed04609ea7e9cc6f3ef3df2
Adds a small fix for some just-rewritten documentation, in commit
4de95f4 ("Mention that standard_kconfig() returns the Kconfig
instance").
Mention that standard_kconfig() returns the Kconfig instance2019-10-10T09:49:21ZUlf Magnussonulfalizer@gmail.com2019-10-10T09:49:21Zurn:sha1:4de95f410fd4c170f5ccdb9a4c74d383e0574d55
Accidentally left out when the docstring was rewritten.
allnoconfig: Comment nit2019-10-10T09:30:12ZUlf Magnussonulfalizer@gmail.com2019-10-10T09:30:12Zurn:sha1:bed364906faa6fa1b55c39607f9e2e65bd565d59Make 13.1.0 release2019-10-10T09:02:20ZUlf Magnussonulfalizer@gmail.com2019-10-10T08:47:57Zurn:sha1:13902e1942f0ac25f3002908520cbe68f31a1a5f
- Commit e016deb ("Convert standard_kconfig() to argparse for better
feedback") improves feedback from the tools and makes their help
texts easier to find
- Commit 0f56dd9 ("guiconfig: Check for visible nodes before turning
off show-all in full-tree mode") fixes an obscure bug in show-all
mode in guiconfig
testsuite: Remove unused imports2019-10-10T09:02:20ZUlf Magnussonulfalizer@gmail.com2019-10-10T09:01:54Zurn:sha1:2a6ade98bc73623d945fa7cef816dcfc60960883
Reported by pylint.
guiconfig: Check for visible nodes before turning off show-all in full-tree mode2019-10-10T08:37:54ZUlf Magnussonulfalizer@gmail.com2019-10-10T08:34:22Zurn:sha1:0f56dd918b022c84cba63a810c75a386a7fe38b3
If there are no visible nodes in the entire tree, guiconfig
automatically starts in show-all mode. Previously, there was no check
for visible nodes when turning off show-all in full-tree mode in this
case, leading to errors.
Fix it by checking if there are any visible nodes in the top menu when
turning off show-all in full-tree mode. If there aren't, show-all stays
on.