toggle quoted messageShow quoted text
From: Cufi, Carles
Sent: 28 January 2019 09:43
To: zephyr-devel <firstname.lastname@example.org>; zephyr-
Subject: Introducing west, Zephyr's meta-tool
For a few months now we have been working on a meta-tool named west,
designed to act both as a command-line tool to build, flash an debug
Zephyr-based applications and also to manage the additional Git
repositories that Zephyr will require in order to build in the near
West is written in Python 3, lives in its own repository  and its
bootstrapper is available on PyPi .
As soon as we merge the topic-west  branch into master (which should
happen in the next few days) you will need to install west in order to
flash and debug, since those commands will rely on havig west present as
part of your Zephyr workflow.
The updated west documentation will be online in the Zephyr
documentation website  as soon as the topic-west branch is merged
into master. In the meantime you can also look at the unrendered
documentation sources in the topic-west branch  and the existing
GitHub issues .
In order to install the west boostrapper (which you can do today) run:
# On Linux
pip3 install --user west
# On macOS and Windows
pip3 install west
Once the west bootstrapper is installed and the topic-west branch is
merged into master, you will have 2 choices to get a west main
1. Clone a new copy of the zephyr repository using west:
west init zephyrproject
2. Install west around an existing local zephyr clone:
Move the cloned zephyr/ repository to an empty enclosing folder (for
example zephyrproject/zephyr/), and from this enclosing folder
west init -l zephyr/
The -l <path to zephyr> parameter instructs west to use an existing
local copy instead of cloning a remote repository.
Feedback and patches are welcome, but note that the feature will likely
be merged as-is since we consider we have left ample time to raise any
major issues regarding the workflow and decisions taken during the
development of west. This is however only the beginning of west's
(hopefully) long existence as the Zephyr command-line meta-tool, and it
will certainly evolve and change considerably in the future with the
help of the community.
Please submit feedback in the form of GitHub issues on the west
repository itself  unless it affects features or functionality in the
zephyr repository directly.
I will reply to this email once the topic-west branch is merged into
Thank you to everybody who has contributed so far!