mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-08-08 22:17:47 +00:00
3a88dce9c5
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> |
||
|---|---|---|
| .. | ||
| runners | ||
| tests | ||
| build.py | ||
| debug.py | ||
| flash.py | ||
| README.txt | ||
| run_common.py | ||
| sign.py | ||
| zephyr_ext_common.py | ||
This directory contains implementations for west commands which are
tightly coupled to the zephyr tree. Currently, those are the build,
flash, and debug commands.
Before adding more here, consider whether you might want to put new
extensions in upstream west. For example, any commands which operate
on the multi-repo need to be in upstream west, not here. Try to limit
what goes in here to just those files that change along with Zephyr
itself.
When extending this code, please keep the unit tests (in tests/) up to
date. You can run the tests with this command from this directory:
$ PYTHONPATH=$(west list --format="{abspath}" west)/src:$PWD py.test
Windows users will need to find the path to .west/west/src in their
Zephyr installation, then run something like this:
> cmd /C "set PYTHONPATH=path\to\.west\west\src:path\to\zephyr\scripts\west_commands && py.test"
Note that these tests are run as part of Zephyr's CI when submitting
an upstream pull request, and pull requests which break the tests
cannot be merged.
Thanks!