Kconfiglib.git/tests, branch v10.8.1Fork of https://github.com/zephyrproject-rtos/Kconfiglib.githttps://git.mcdonnell.dev/Kconfiglib.git/atom?h=v10.8.12018-09-23T18:22:30ZFix formatting nit in user-defined Python function tests2018-09-23T18:22:30ZUlf Magnussonulfalizer@gmail.com2018-09-23T18:20:49Zurn:sha1:a3f37faed0aaa024fa6354a429ace427a6dc807cAdd support for user-defined Python preprocessor functions2018-09-23T15:31:20ZUlf Magnussonulfalizer@gmail.com2018-09-20T11:33:59Zurn:sha1:6156041560c75831e003202b790ab3f435bbb388
Allow preprocessor functions to be defined in Python by putting a module
called 'kconfigfunctions' into sys.path. Internally, this simply adds
the functions to the predefined functions in Kconfig._functions.
User-defined Python functions make it simple to integrate information
from existing Python tools into Kconfig, e.g. to have Kconfig symbols
depend on hardware information stored in some other format. This might
be used to get device tree information into Kconfig in Zephyr.
Piggyback module docstring documentation for some extensions that were
previously only mentioned in the README.
Allow macro expansion within symbol names2018-09-04T18:49:21ZUlf Magnussonulfalizer@gmail.com2018-09-04T16:05:28Zurn:sha1:a092257a49ed7850913cf53e474f4c8dd175c94b
The C implementation supports this (though it's undocumented, and unused
to far).
This can be used e.g. to dynamically instatiate symbols from template
files:
Kconfig.template:
config $(subsys)_LOG
bool "Enable logging for $(subsys)"
depends on $(subsys)_HAS_LOG
... other stuff dependent on $(subsys)
Elsewhere:
subsys = FOO
source "Kconfig.template"
subsys = BAR
source "Kconfig.template"
Pretty sure this can easily be abused, but it should be supported at
least.
Add a Kconfig.env_vars attribute that lists env. variables2018-08-25T18:32:34ZUlf Magnussonulfalizer@gmail.com2018-08-25T18:07:05Zurn:sha1:932d0f7b8a69bdcac5d945de600ce6be807aeff7
Kconfig.env_vars is a set() with the names of all environment variables
referenced in the configuration.
Can be used e.g. for custom incremental build implementations, though
sync_deps() already indirectly catches any relevant changes to
environment variables.
Show include paths in menuconfig symbol information2018-08-23T23:01:36ZUlf Magnussonulfalizer@gmail.com2018-08-23T00:43:00Zurn:sha1:13884e934ec8eda928234c6506ae27f0334ec31b
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.
Fix recursive 'source' error reporting2018-08-23T09:42:49ZUlf Magnussonulfalizer@gmail.com2018-08-23T08:45:42Zurn:sha1:3aca83eaf20f5e278b6d260cb255e6a9385590db
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.
Make header symbol order match .config symbol order again2018-08-21T13:19:52ZUlf Magnussonulfalizer@gmail.com2018-08-21T12:08:55Zurn:sha1:d78c293c41351256f76fb2fa27e72e399b130e4f
I accidentally broke this when I added the _defined_syms_set
optimization. No semantic difference, but having the order match is more
readable.
Fix detection of hex literals2018-07-20T20:09:51ZUlf Magnussonulfalizer@gmail.com2018-07-20T20:03:43Zurn:sha1:2d391d8f369a40b438a1b246c888bb42b2e14278
Missing 'not'. Add some literals to the Kstrict testcase.
Add KCONFIG_STRICT flag for flagging refs. to undefined syms2018-07-20T19:15:23ZUlf Magnussonulfalizer@gmail.com2018-07-20T02:14:31Zurn:sha1:ca89d02ca1639b72c7b74834ff432ab10df58fe9
Settings KCONFIG_STRICT to y in the environment turns on warnings for
all references to undefined symbols within Kconfig files (with the only
gotcha that hex literals must be prefixed by 0x or 0X, to make it
possible to distinguish them from undefined references).
Always flagging undefined references gets awkward, as some projects
(e.g. the Linux kernel) use multiple Kconfig trees with shared files,
leading to some safe undefined references. It's helpful for other
projects though.
Having KCONFIG_STRICT as an environment variable is handy when multiple
tools are involved.
Piggyback a small README change re. warnings. Kconfiglib now has many
more warnings than the C tools.
Add def_int, def_hex, and def_string keywords2018-07-18T01:23:43ZUlf Magnussonulfalizer@gmail.com2018-07-18T01:05:37Zurn:sha1:e08b6957ca935fc97eddd1afda933715016b9b11
Analogous to def_bool and def_tristate, setting the type and adding a
default at the same time.
This is a Kconfiglib extension. These keywords can be useful in projects
that make use of symbols defined in multiple locations, and remove some
Kconfig inconsistency.