Kconfiglib.git/testsuite.py, branch v10.2.1

Show include paths in menuconfig symbol information

2018-08-23T23:01:36Z

Add a MenuNode.include_path attribute that holds a tuple of (filename, linenr) tuples, giving the locations of the 'source' statements via which the node's Kconfig file was included, starting from the top-level Kconfig file. Use MenuNode.include_path to give the include path for symbols and other items in the help display in the menuconfig interface. This is useful for figuring out how Kconfig files are organized, and when reorganizing things.

Exclude User-mode Linux from testing

2018-08-23T09:42:49Z

This "architecture" has an unorthodox Kconfig setup that would require a different testing setup.

Fix recursive 'source' error reporting

2018-08-23T09:42:49Z

The recursive 'source' detection was still fine, but the error reporting had broken due a missed variable renaming. The test suite didn't catch it, because a different type of KconfigError was raised instead, due to a separate error in the test suite (need to include tests/Krecursive{1,2}, since paths are relative to $srctree). Fix the variable name and tighten up the tests to check that the KconfigError message is the one we except. Tighten up the dependency loop detection tests in the same way too.

Flag extra tokens after 'if'/'depends on'/'visible if' expressions

2018-08-22T22:51:52Z

Extra trailing tokens after 'if ', 'depends on ', and 'visible if ' now trigger syntax errors instead of being ignored. Oversight. This indirectly makes Kconfig.eval_expr() detect extra trailing tokens as well.

Add a generic node iterator

2018-08-22T21:57:17Z

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.

Merge Symbol._checked and Symbol._written

2018-08-21T19:17:45Z

These are never used at the same time, and Symbol._visited is a good name for both. Gets rid of an internal attribute.

Handle multiple definition locations in a nicer way

2018-08-21T18:45:27Z

Instead of precalculating a set() to get unique symbols, precalculate a list with any duplicates from multiple definition locations removed, and preserve the order of the symbols within it. This makes it possible to get rid of the Symbol._written shenanigans in functions that only need to iterate through unique symbols in sorted order, which is all of them except write_config() (because it needs to walk the entire menu tree).

Fix header/minimal configuration ordering test

2018-08-21T13:40:53Z

Should test write_autoconf(), not write_config().

Make header symbol order match .config symbol order again

2018-08-21T13:19:52Z

I accidentally broke this when I added the _defined_syms_set optimization. No semantic difference, but having the order match is more readable.

Look up the top-level Kconfig file relative to $srctree

2018-08-18T01:15:46Z

Due to an old design braino, the top-level Kconfig filename passed to Kconfig.__init__() wasn't looked up relative to $srctree, breaking out-of-tree usage for e.g. menuconfig. Fixing it required ugliness like srctree = os.environ.get("srctree", "") kconfiglib.Kconfig(os.path.join(srctree, "Kconfig")) Change the behavior of Kconfig.__init__() to look up the top-level Kconfig file relative to $srctree. This means that all Kconfig files (both the top-level file and any source'd files) now use $srctree, which makes the vast majority of scripts just work when running out-of-tree. Also remove the note re. loading a subset of Kconfig files. Saying that the top-level file and all source'd Kconfig files are looked up relative to $srctree should make the behavior clear enough. Print a note about the new behavior whenever the top-level Kconfig file can't be opened, as this change could be breaking for some scripts. This is a slight backwards-compatiblity break, so the major version will be bumped.