History and Motivation

West was added to the Zephyr project to fulfill two fundamental requirements:

• The ability to work with multiple Git repositories

• The ability to provide an extensible and user-friendly command-line interface for basic Zephyr workflows

During the development of west, a set of Design Constraints were identified to avoid the common pitfalls of tools of this kind.

Requirements

Although the motivation behind splitting the Zephyr codebase into multiple repositories is outside of the scope of this page, the fundamental requirements, along with a clear justification of the choice not to use existing tools and instead develop a new one, do belong here.

The basic requirements are:

• R1: Keep externally maintained code in separately maintained repositories outside of the main zephyr repository, without requiring users to manually clone each of the external repositories

• R2: Provide a tool that both Zephyr users and distributors can make use of to benefit from and extend

• R3: Allow users and downstream distributions to override or remove repositories without having to make changes to the zephyr repository

• R4: Support both continuous tracking and commit-based (bisectable) project updating

Rationale for a custom tool

Some of west’s features are similar to those provided by Git Submodules and Google’s repo.

Existing tools were considered during west’s initial design and development. None were found suitable for Zephyr’s requirements. In particular, these were examined in detail:

• Google repo

  • Does not cleanly support using zephyr as the manifest repository (R4)

  • Python 2 only

  • Does not play well with Windows

  • Assumes Gerrit is used for code review

• Git submodules

  • Does not fully support R1, since the externally maintained repositories would still need to be inside the main zephyr Git tree

  • Does not support R3, since downstream copies would need to either delete or replace submodule definitions

  • Does not support continuous tracking of the latest HEAD in external repositories (R4)

  • Requires hardcoding of the paths/locations of the external repositories

Multiple Git Repositories

Zephyr intends to provide all required building blocks needed to deploy complex IoT applications. This in turn means that the Zephyr project is much more than an RTOS kernel, and is instead a collection of components that work together. In this context, there are a few reasons to work with multiple Git repositories in a standardized manner within the project:

• Clean separation of Zephyr original code and imported projects and libraries

• Avoidance of license incompatibilities between original and imported code

• Reduction in size and scope of the core Zephyr codebase, with additional repositories containing optional components instead of being imported directly into the tree

• Safety and security certifications

• Enforcement of modularization of the components

• Out-of-tree development based on subsets of the supported boards and SoCs

See Basics for information on how west workspaces manage multiple git repositories.

Design Constraints

West is:

• Optional: it is always possible to drop back to “raw” command-line tools, i.e. use Zephyr without using west (although west itself might need to be installed and accessible to the build system). It may not always be convenient to do so, however. (If all of west’s features were already conveniently available, there would be no reason to develop it.)

• Compatible with CMake: building, flashing and debugging, and emulator support will always remain compatible with direct use of CMake.

• Cross-platform: West is written in Python 3, and works on all platforms supported by Zephyr.

• Usable as a Library: whenever possible, west features are implemented as libraries that can be used standalone in other programs, along with separate command line interfaces that wrap them. West itself is a Python package named west; its libraries are implemented as subpackages.

• Conservative about features: no features will be accepted without strong and compelling motivation.

• Clearly specified: West’s behavior in cases where it wraps other commands is clearly specified and documented. This enables interoperability with third party tools, and means Zephyr developers can always find out what is happening “under the hood” when using west.

See Zephyr issue #6205 and for more details and discussion.

west update detached HEADs

The use of detached git HEAD revisions documented in the update procedure confuses and even frustrates some users.

Specifically, users often ask why west update doesn’t leave existing local branches checked out by default.

This section explains why west update behaves the way it does by default, and mentions some other options you have for managing projects that you modified locally.

Two core requirements for west update are:

1. safety: the command should not lose any of the user’s work

2. determinism: two users running west update on the same manifest should get the exact same workspace contents

Using detached HEADs helps preserve safety. As documented in the update procedure, using git checkout --detach on the updated project to get a detached HEAD is a generally safe operation that won’t lose the user’s work:

• if your work is all safely committed in a local git branch, that branch will be left as-is (see the git help checkout output for details)

• if you have uncommitted work, it will be safely kept in your working tree by git if that’s possible

• if that’s not possible, the entire command will fail, and you can decide what to do with your work before re-running west update

Detached HEADs also help ensure determinism:

• Checking out exactly the project revision that’s specified in your manifest file is needed to make sure your workspace’s files match what’s specified in the main manifest. If west did not check out the manifest revision by default, your workspace could be invisibly different from what you would expect given the contents of the manifest files in your working copy. Even worse, the way it was different would depend on exactly what was in your branch before you ran west update.

• There is a subtle interaction with Manifest Imports. If your project itself has one or more manifest files that are being imported by west update, then west needs to check out those files into the working tree so it can resolve the entire imported manifest. If west update left a branch checked out in your project, the manifest files in your working tree could be out of date. If west then used those out-of-date files to finish the import, the process could fail unexpectedly or produce other nondeterministic results.

West does not check out the manifest-rev branch directly for reasons explained in the documentation for that branch.

This default behavior was chosen a long time ago and it’s too late to change it now, since users are depending on it. However, there are other ways to run west update if this default doesn’t work for you. To learn more, run west help update and read the checked out branch behavior option group text. For example:

• if you’re actively writing some code in your project and you want to keep it up to date after potential changes in the upstream manifest, use west update --rebase

• if you’ve got some local code you’d like to keep around as long as the upstream revision for your project hasn’t moved on to something newer, use west update --keep-descendants

You can use West aliases if you want to set up a shorter way to type one of these commands in your workspace. You can also contribute new options to this option group by sending a pull request to:

https://github.com/zephyrproject-rtos/west