Fork of https://github.com/zephyrproject-rtos/Kconfiglib.git https://git.mcdonnell.dev/Kconfiglib.git/atom?h=v11.5.0 2018-05-16T17:42:56Z 2018-05-16T17:42:56Z Ulf Magnusson ulfalizer@gmail.com 2018-05-14T16:00:40Z urn:sha1:cbf32e29a130d22bc734b7778e6304ac9df2a3e8 Make "$FOO" directly reference the environment variable $FOO in e.g. 'source' statements, instead of the symbol FOO. Use os.path.expandvars() to expand strings (which preserves "$FOO" as-is if no environment variable FOO exists). This gets rid of the 'option env' "bounce" symbols, which are mostly just spam and are buggy in the C tools (dependencies aren't always respected, due to parsing and evaluation getting mixed up). The same change will probably appear soon in the C tools as well. Keep accepting 'option env' to preserve some backwards compatibility, but ignore it when expanding strings. For compatibility with the C tools, bounce symbols will need to be named the same as the environment variables they reference (which is the case for the Linux kernel). This is a compatibility break, so the major version will be bumped to 6 at the next release. The main motivation for adding this now is to allow recording properties on each MenuNode in a clean way. 'option env' symbols interact badly with delayed dependency propagation. Side note: I have a feeling that recording environment variable values might be redundant to trigger rebuilds if sync_deps() is run at each compile. It should detect all changes to symbol values due to environment variables changing value. 2017-10-24T17:24:08Z Ulf Magnusson ulfalizer@gmail.com 2017-10-09T21:05:00Z urn:sha1:dd0e227216e247d2040cdd40bf7397702880cdc4 WIP 2012-12-11T10:43:19Z Ulf Magnusson ulfalizer@gmail.com 2012-12-11T10:42:07Z urn:sha1:f7cc4fbcc769b23dad05ad0b8d21ec650ac01037