Lines Matching refs:west
6 This page describes the *west workspace* concept introduced in
7 :ref:`west-basics` in more detail.
16 specified for the project at the time :ref:`west-update` was last run.
22 Although ``manifest-rev`` is a normal Git branch, west will recreate and/or
25 you manually add to this branch may be lost the next time you run ``west
33 since west does not manage the manifest repository's branches or revisions.
35 The ``refs/west/*`` Git refs
38 West also reserves all Git refs that begin with ``refs/west/`` (such as
39 ``refs/west/foo``) for itself in local project repositories. Unlike
47 You can use west to fetch from private repositories. There is nothing
48 west-specific about this.
50 The ``west update`` command essentially runs ``git fetch YOUR_PROJECT_URL``
56 no need for a west-specific feature.
58 The following sections cover common cases for running ``west update`` without
79 west forall -c "git config credential.helper store"
85 west forall -c "git config credential.helper store" foo bar
147 symbolic link to elsewhere on your computer, but west will not do this for you.
154 The following are example source code topologies supported by west.
164 its :ref:`modules` in its :file:`west.yml`
168 This is the default. See :ref:`west-workspace` for how mainline Zephyr is an
178 and names other projects required to build it in its :file:`west.yml`. This
187 west-workspace/
191 │ ├── prj.conf │ never modified by west
194 │ └── west.yml # main manifest with optional import(s) and override(s)
201 └── west.yml # This can be partially imported with lower precedence or ignored.
205 Here is an example :file:`application/west.yml` which uses
206 :ref:`west-manifest-import`, available since west 0.7, to import Zephyr v2.5.0
211 # Example T2 west.yml, using manifest imports.
225 ``import:`` in this way; see :ref:`west-manifest-ex1.3` for an example.
227 Another way to do the same thing is to copy/paste :file:`zephyr/west.yml`
228 to :file:`application/west.yml`, adding an entry for the zephyr
243 west-commands: scripts/west-commands.yml
251 (The ``west-commands`` is there for :ref:`west-build-flash-debug` and other
252 Zephyr-specific :ref:`west-extensions`. It's not necessary when using
258 :file:`zephyr/west.yml` revision, instead of having to be copy/pasted (and
274 west-workspace/
285 ├── manifest-repo/ # .git/ never modified by west
286 │ └── west.yml # main manifest with optional import(s) and override(s)
293 └── west.yml # This can be partially imported with lower precedence or ignored.
296 Here is an example T3 :file:`manifest-repo/west.yml` which uses
297 :ref:`west-manifest-import`, available since west 0.7, to import Zephyr
322 You can also do this "by hand" by copy/pasting :file:`zephyr/west.yml`
323 as shown :ref:`above <west-t2>` for the T2 topology, with the same caveats.