Carles Cufi 3a88dce9c5 scripts: west: Run pristine.cmake directly instead of the target ... When making a build folder pristine until now we were running the 'pristine' build target. The issue with that is that ninja/make or whatever build tool is being used might decide to re-run CMake itself if some of the dependencies have changes. This might trigger an error that is unfriendly and unnecessary, since the user is explicitly asking for the build folder to be wiped before starting a fresh build. To avoid this issue restor to running directly the CMake script that the 'pristine' build target itself uses, so as to make sure that the build folder is wiped unconditionally regardless of changes made to the tree. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>		2019-04-23 13:24:41 -07:00
..
build-flash-debug.rst	west: build: Add new pristine cmd-line and config option	2019-04-17 10:02:46 -04:00
config.rst	scripts: west: Run pristine.cmake directly instead of the target	2019-04-23 13:24:41 -07:00
extensions.rst
index.rst
manifest.rst
planned.rst	doc: add missing doc top labels	2019-04-16 18:11:30 -04:00
repo-tool.rst
sign.rst
west-apis.rst
west-mr-model.png
west-not-found.rst
why.rst
without-west.rst