Kconfiglib.git/tests/Kpreprocess, branch v10.26.0Fork of https://github.com/zephyrproject-rtos/Kconfiglib.githttps://git.mcdonnell.dev/Kconfiglib.git/atom?h=v10.26.02018-09-04T18:49:21ZAllow 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.
Add Kconfig preprocessor2018-07-10T05:56:37ZUlf Magnussonulfalizer@gmail.com2018-07-03T16:30:06Zurn:sha1:2433deba7889931c4bae679f116887fe49a2ce04
Implement the Kconfig preprocessor described in
https://github.com/torvalds/linux/blob/master/Documentation/kbuild/kconfig-macro-language.txt
(which is now in linux-next and will appear in Linux 4.18).
A new Kconfig.variables property holds all the preprocessor variables so
that they can be inspected programmatically. Preprocessor variables are
represented by a new Variable class.
With the preprocessor, environment variables are referenced with $(FOO)
instead of $FOO. For backwards compatibility, $FOO is accepted as well
for now (and leaves "$FOO" as-is if FOO doesn't exist). The $FOO syntax
might be dropped at some point in the future (together with a major
version increase). It should be supported for a few months at least.
Some internals were cleaned up too, mostly related to parsing. Some
outdated documentation was fixed as well.