Torsten Rasmussen d7862cf776 cmake: using ${ZEPHYR_BASE} instead of $ENV{ZEPHYR_BASE} ... With the introduction of ZephyrConfig.cmake all parts of CMake code should rely on the CMake ZEPHYR_BASE variable instead of the environment setting. This ensures that after the first CMake invocation, then all subsequent invocation in same build folder will use same zephyr base. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>		2020-03-27 16:23:46 +01:00
..
diffconfig	license: cleanup: add SPDX Apache-2.0 license identifier	2019-04-07 08:45:22 -04:00
guiconfig.py	kconfig/devicetree: Print path to headers when configuring	2020-01-31 19:45:43 +01:00
hardenconfig.py	hardening: Introducing hardenconfig tool	2019-12-09 12:54:29 -05:00
hardened.csv	hardening: Introducing hardenconfig tool	2019-12-09 12:54:29 -05:00
kconfig.py	cmake: using ${ZEPHYR_BASE} instead of $ENV{ZEPHYR_BASE}	2020-03-27 16:23:46 +01:00
kconfigfunctions.py	edtlib: allow register addr / size to be None	2020-03-24 10:11:20 -05:00
kconfiglib.py	kconfig/devicetree: Print path to headers when configuring	2020-01-31 19:45:43 +01:00
lint.py	scripts: kconfig: lint.py: Add check for missing CONFIG_ prefix	2020-01-31 19:29:49 +01:00
menuconfig.py	kconfig/devicetree: Print path to headers when configuring	2020-01-31 19:45:43 +01:00