Ulf Magnusson 5402662dd9 cmake: kconfig: Fix rerunning cmake after Kconfig warnings ... Commit b3d165f ("scripts: kconfig: Handle warnings generated during evaluation") made it common for kconfig.py to fail after writing zephyr/.config. This confuses the configuration fragment checksum logic in cmake/kconfig.cmake, because it expects the saved checksum file to exist if zephyr/.config exists. The end result is a CMake error when rerunning the configuration after non-whitelisted Kconfig warnings. Fix it by only writing zephyr/.config (and zephyr/include/autoconf.h) in kconfig.py if there are no warnings-turned-errors. Also check if the saved checksum file exists in kconfig.cmake before trying to open it. Normally this shouldn't happen though. Move the writing of the checksum file to before writing zephyr/.config as well. That way, zephyr/.config only gets written if the other operations succeed. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>		2018-08-02 19:15:26 +02:00
..
checkconfig.py	kconfig: Mention that checkconfig.py lacks Kconfiglib 2 support	2018-05-07 21:53:37 +02:00
diffconfig	scripts: move kconfig related scripts to scripts/kconfig	2017-09-11 08:53:56 -07:00
kconfig.py	cmake: kconfig: Fix rerunning cmake after Kconfig warnings	2018-08-02 19:15:26 +02:00
kconfiglib.py	kconfiglib: Fix paths for gsource'd files in the documentation	2018-07-14 08:17:58 +02:00
menuconfig.py	menuconfig: Allow searches from the info dialog and vice versa	2018-06-18 14:41:53 -04:00