2b3d9df1d7
The main change is the elimination of the bootstrapper, a design flaw / misfeature. Update the documentation to be compatible with the 0.6.x releases as well. This has to be done atomically, as there were incompatible changes. Make use of the versionchanged and versionadded directives to begin keeping track of how these APIs are evolving. (Note that west 0.6.0 will remain compatible with the extension commands in Zephyr v1.14 LTS as long as that is still alive. This change is targeted towards Zephyr 2.0 users.) This requires a bump in the shippable container and allows us to simplify the west_commands test procedure. Signed-off-by: Marti Bolivar <marti.bolivar@nordicsemi.no>
26 lines
971 B
Plaintext
26 lines
971 B
Plaintext
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=$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\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!
|