Kconfiglib.git/examples, branch v10.1.0Fork of https://github.com/zephyrproject-rtos/Kconfiglib.githttps://git.mcdonnell.dev/Kconfiglib.git/atom?h=v10.1.02018-08-22T21:57:17ZAdd a generic node iterator2018-08-22T21:57:17ZUlf Magnussonulfalizer@gmail.com2018-08-22T20:08:06Zurn:sha1:7dae98803a6fc5d08041d1387e2e0d83fc0eb0ed
Suggested by Mitja Horvat (pinkfluid) in
https://github.com/ulfalizer/Kconfiglib/pull/50.
Kconfig.node_iter() iterates through all menu nodes in the menu tree in
Kconfig order. This saves scripts the trouble of implementing their own
tree walking code.
Have node_iter() take a 'unique_syms' flag that can be enabled to only
include symbols defined in multiple locations once. This is often what
you want when generating output (and is used by write_config()). Order
is still preserved.
Piggyback a fix to a syntax error test comment. Parsing has been
tightened up now.
Introduce Kconfig.unique_defined_syms and Kconfig.unique_choices2018-08-22T18:05:11ZUlf Magnussonulfalizer@gmail.com2018-08-22T00:25:20Zurn:sha1:d2c1430c91c574dc0dfd84f3652c8d9af8c77568
These are the same as Kconfig.defined_syms and Kconfig.choices, except
duplicates are removed. Kconfig order is still preserved.
This is almost always what you want when iterating through symbols and
choices, as it potentially saves work, avoids generating duplicates when
writing output, and still preserves Kconfig order for readability.
The old attributes will be kept for backwards compatibility (maybe
there's some rare cases where they could be useful too). They're created
internally anyway.
Simplify the find_symbol and list_undefined examples2018-06-22T07:03:48ZUlf Magnussonulfalizer@gmail.com2018-06-22T05:27:54Zurn:sha1:4503fccb7ab07c190902618cfab6f6559c611a95
Much of the functionality is available in Kconfiglib itself now. Use the
new APIs to implement the examples in a much simpler way.
Add a function for getting all items in an expression2018-06-11T16:30:51ZUlf Magnussonulfalizer@gmail.com2018-06-11T15:49:49Zurn:sha1:506e3fb211d22f62115ce83e9247266c5d87ea24
Handy e.g. when searching.
allyesconfig: Prepare for packaging2018-05-30T17:10:58ZUlf Magnussonulfalizer@gmail.com2018-05-30T16:05:04Zurn:sha1:38cca3bdeca7d91044e11ddf2193e07c5d223ad3
Move to the root, simplify a bit, provide an entry point function (for
setuptools's entry_points).
Simplify allyesconfig.py example with Kconfig.choices2018-05-27T22:41:35ZUlf Magnussonulfalizer@gmail.com2018-05-27T22:18:06Zurn:sha1:b95477a82d0a5bc4218aa00c8a76edc3c95d8d4f
Could do something similar to allnoconfig.py for the packaged version.
allnoconfig: Move from examples/ to root2018-05-27T18:37:59ZUlf Magnussonulfalizer@gmail.com2018-05-27T18:37:59Zurn:sha1:4c4f184a3a648b8cb748ab35159a09ccd06b2ff7
Put to-be-packaged stuff in the root.
Use allnoconfig_simpler.py, and rename allnoconfig.py to
allnoconfig_walk.py and keep it as an example.
oldconfig: Move from examples/ to root2018-05-27T17:18:40ZUlf Magnussonulfalizer@gmail.com2018-05-27T17:18:40Zurn:sha1:81a0b2ede3f59784d271a60701291e2a0dfc2a7d
All the packaged code will appear in the root.
oldconfig: Prepare for packaging2018-05-27T16:45:33ZUlf Magnussonulfalizer@gmail.com2018-05-27T16:34:50Zurn:sha1:58234d60b45ff5a8c04caf2cb5a18f77252cdbca
setuptools' 'entry_points' gives nice behavior on Windows. It requires
that the module has an entry point function. Create one and move the
command line argument handling to it.
Piggyback KCONFIG_CONFIG support, and make the script executable
(oversight).
oldconfig: Show help with '?' instead of '??'2018-05-27T15:47:50ZUlf Magnussonulfalizer@gmail.com2018-05-27T15:47:50Zurn:sha1:5b2eebea674012bd4ca6b965c901e8868375b778
This matches the C tools. Hadn't noticed they had the same feature.