| /Zephyr-Core-3.5.0/doc/develop/west/ |
| D | manifest.rst | 7 manifest files, and the ``west manifest`` command. For API documentation on the
8 ``west.manifest`` module, see :ref:`west-apis-manifest`. For a more general
32 The history of the manifest repository is the line of Git commits which is
39 The commits in the manifest repository (again, for upstream Zephyr this is the
40 zephyr repository itself) each have a manifest file. The manifest file in each
43 diagram. Each dotted line arrow points from a commit in the manifest repository
48 - Projects can be added (like ``P1`` between manifest repository
50 manifest repository commits)
52 - Project and manifest repository histories don't have to move
67 the same time": every manifest file refers to exactly one commit in
[all …]
|
| D | basics.rst | 24 │ # The manifest repository, never modified by west after creation:
26 │ ├── west.yml # manifest file
63 manifest repository
64 Every west workspace contains exactly one *manifest repository*, which is a
65 Git repository containing a *manifest file*. The location of the manifest
66 repository is given by the :ref:`manifest.path configuration option
69 For upstream Zephyr, :file:`zephyr` is the manifest repository, but you can
70 configure west to use any Git repository in the workspace as the manifest
71 repository. The only requirement is that it contains a valid manifest file.
73 :ref:`west-manifests` for details on the manifest file format.
[all …]
|
| D | built-in.rst | 14 names as specified in the manifest file, or (as a fallback) paths to them
17 to using all projects in the manifest file plus the manifest repository
29 1. Cloning a new manifest repository from a remote URL
30 2. Creating a workspace around an existing local manifest repository
32 **Option 1**: to clone a new manifest repository from a remote URL, use:
39 :file:`.west` inside this directory. You can give the manifest URL using
41 the location of the manifest file within the repository using ``--mf``.
51 :file:`zp/.west`, and set the ``manifest.path`` :ref:`configuration option
52 <west-config>` to ``zephyr`` to record the location of the manifest
53 repository in the workspace. The default manifest file location is used.
[all …]
|
| D | release-notes.rst | 12 workspace against the manifest.
14 - Support for a new ``manifest.project-filter`` configuration option.
15 See :ref:`west-config-index` for details. The ``west manifest --freeze``
16 and ``west manifest --resolve`` commands currently cannot be used when
20 warnings. These warnings are errors if the new ``manifest.project-filter``
41 - ``west.manifest.Manifest.is_active()`` now respects the
42 ``manifest.project-filter`` configuration option's value.
51 used by applications that do not wish to use a "0.x" manifest "version:"
52 field. See :ref:`west-manifest-schema-version` for details on this feature.
145 open the manifest file instead of dumping stack traces.
[all …]
|
| D | workspaces.rst | 9 .. _west-manifest-rev:
11 The ``manifest-rev`` branch
14 West creates and controls a Git branch named ``manifest-rev`` in each
15 project. This branch points to the revision that the manifest file
17 Other workspace management commands may use ``manifest-rev`` as a reference
19 purposes, the ``manifest-rev`` branch allows the manifest file to use SHAs
22 Although ``manifest-rev`` is a normal Git branch, west will recreate and/or
27 rebase it on top of a new ``manifest-rev``, or merge ``manifest-rev`` into
32 West does not create a ``manifest-rev`` branch in the manifest repository,
33 since west does not manage the manifest repository's branches or revisions.
[all …]
|
| D | config.rst | 18 [manifest]
24 Above, the ``manifest`` section has option ``path`` set to ``zephyr``. Another
25 way to say the same thing is that ``manifest.path`` is ``zephyr`` in this file.
71 To set ``manifest.path`` to :file:`some-other-manifest`:
75 west config manifest.path some-other-manifest
78 :term:`west manifest` inside the :file:`some-other-manifest` directory
89 You can switch to another zephyr repository without changing ``manifest.path``
98 of the zephyr repository specified in the manifest. (You can go back to using
99 the directory in the upstream manifest by running ``west config zephyr.base
138 * - ``manifest.file``
[all …]
|
| D | west-apis.rst | 69 .. py:attribute:: manifest
71 A property which returns the :py:class:`west.manifest.Manifest`
72 instance for the current manifest file or aborts the program if one was
81 True if reading the manifest property will succeed instead of erroring
305 .. _west-apis-manifest:
307 west.manifest
310 .. automodule:: west.manifest
313 represent the contents of a :ref:`manifest file <west-manifests>`. The
326 .. autofunction:: west.manifest.manifest_path argument
328 .. autofunction:: west.manifest.validate
[all …]
|
| D | west-not-found.rst | 9 .. _west-apis-manifest:
|
| D | extensions.rst | 62 :term:`west manifest`.
73 tracked by your :term:`west manifest`, or the manifest repository itself.
164 - It allows users to run ``west update`` with a manifest from an untrusted
211 just edited in your west manifest. If your extension is in a project, add it
216 manifest:
228 Alternatively, if your extension is in the manifest repository, just do the
229 same thing in the manifest's ``self`` section, like this:
233 manifest:
|
| D | troubleshooting.rst | 24 west.manifest: your_project: checking if cloned
25 [...other west.manifest logs...]
27 …west.manifest: running 'git fetch ... https://github.com/your-username/your_project ...' in /some/…
174 extension commands from project manifest (path: zephyr):
187 (choose from 'init', 'update', 'list', 'manifest', 'diff',
|
| /Zephyr-Core-3.5.0/doc/develop/manifest/ |
| D | index.rst | 22 west config manifest.project-filter -- -hal_FOO
25 .. manifest-projects-table::
39 west config manifest.project-filter -- +nanopb
42 .. manifest-projects-table::
50 default manifest.
51 To use any of the projects below, you will need to define your own manifest
52 file which includes them. See :ref:`west-manifest-import` for information on
|
| /Zephyr-Core-3.5.0/submanifests/ |
| D | README.txt | 1 This directory can contain additional west manifest files. Any files
10 …://docs.zephyrproject.org/latest/guides/west/manifest.html#example-2-2-downstream-with-directory-o…
|
| D | example.yaml.sample | 1 # Example manifest file you can include into the main west.yml file.
14 manifest:
|
| /Zephyr-Core-3.5.0/doc/_extensions/zephyr/ |
| D | manifest_projects_table.py | 36 from west.manifest import Manifest
73 manifest = Manifest.from_file(self.env.config.manifest_projects_table_manifest)
75 for project in manifest.projects:
78 if active_filter == 'active' and manifest.is_active(project):
80 elif active_filter == 'inactive' and not manifest.is_active(project):
|
| D | link-roles.py | 14 import west.manifest
17 west_manifest = west.manifest.Manifest.from_file()
|
| /Zephyr-Core-3.5.0/scripts/west_commands/completion/ |
| D | west-completion.zsh | 14 'update[update projects described in west manifest]'
16 'manifest[manage the west manifest]'
111 '(-l --local)'{--mr,--manifest-rev}'[manifest revision]:manifest rev:'
112 {--mf,--manifest-file}'[manifest file]:manifest file:'
113 '(-l --local)'{-m,--manifest}'[manifest URL]:manifest URL:_directories'
114 …'(-m --manifest --mr --manifest-rev)'{-l,--local}'[use local directory as manifest repository]:loc…
129 {-k,--keep-descendants}'[keep manifest-rev descendants checked out]'
130 {-r,--rebase}'[rebase checked out branch onto the new manifest-rev]'
140 '--manifest-path-from-yaml[print performance stats]'
150 '--resolve[resolve into single manifest]'
[all …]
|
| D | west-completion.fish | 161 "update" "update projects described in west manifest" \
163 "manifest" "manage the west manifest" \
218 …and_from init; and __zephyr_west_exclude -l --local" -l mr -l manifest-rev -r -d "manifest revisio…
219 …e -c west -n "__zephyr_west_seen_subcommand_from init" -l mf -l manifest-file -r -d "manifest file"
220 …d __zephyr_west_exclude -l --local" -o m -l manifest -ra "(__zephyr_west_complete_directories)" -d…
221 …t_exclude -m --manifest --mr --manifest-rev" -o l -l local -ra "(__zephyr_west_complete_directorie…
224 … -c west -n __zephyr_west_use_subcommand -ra update -d "update projects described in west manifest"
232 …hyr_west_seen_subcommand_from update" -o k -l keep-descendants -d "keep manifest-rev descendants c…
233 …een_subcommand_from update" -o r -l rebase -d "rebase checked out branch onto the new manifest-rev"
239 …een_subcommand_from list; and not __fish_seen_subcommand_from blobs" -l manifest-path-from-yaml -d…
[all …]
|
| /Zephyr-Core-3.5.0/scripts/ |
| D | zephyr_module.py | 455 from west.manifest import MANIFEST_REV_BRANCH
517 def west_projects(manifest = None): argument
524 from west.manifest import Manifest
534 from west.manifest import \
542 if not manifest:
543 manifest = Manifest.from_file()
545 projects = [p for p in manifest.get_projects([])
546 if manifest.is_active(p)]
548 projects = manifest.get_projects([])
549 manifest_path = manifest.path
[all …]
|
| D | set_assignees.py | 14 from west.manifest import Manifest
15 from west.manifest import ManifestProject
269 manifest = Manifest.from_file()
272 for project in manifest.get_projects([]):
273 if not manifest.is_active(project):
|
| /Zephyr-Core-3.5.0/samples/tfm_integration/tfm_secure_partition/dummy_partition/ |
| D | tfm_manifest_list.yaml.in | 18 "manifest": "${APPLICATION_SOURCE_DIR}/dummy_partition/tfm_dummy_partition.yaml",
|
| /Zephyr-Core-3.5.0/doc/ |
| D | glossary.rst | 100 west manifest
106 west manifest repository
108 :term:`west manifest`. Its location is given by the :ref:`manifest.path
113 a :term:`west manifest repository`. You clone the Zephyr source
|
| /Zephyr-Core-3.5.0/doc/contribute/ |
| D | external.rst | 106 Integration in main manifest file (west.yaml)
109 Integrating external code into the main :file:`west.yml` manifest file is
125 platform shall be added to an optional manifest file that is filtered by
144 Zephyr project manifest with documentation instructing users and developers how
227 project in the main :file:`west.yml` manifest. Therefore, this section does not
247 :file:`west.yml` manifest. More info on optional projects can be found in
248 :ref:`this section <west-manifest-groups>`.
254 Additional considerations about the main manifest
258 the `main manifest file`_ requires TSC approval. This includes, but is not
265 .. _main manifest file:
|
| /Zephyr-Core-3.5.0/cmake/modules/ |
| D | FindBabbleSim.cmake | 16 # fetched babblesim using the manifest.
48 west config manifest.group-filter +babblesim && west update\n\
|
| /Zephyr-Core-3.5.0/modules/ |
| D | Kconfig.sysbuild | 10 comment "Unavailable modules, please install those via the project manifest."
|
| /Zephyr-Core-3.5.0/scripts/west_commands/ |
| D | boards.py | 77 for module in zephyr_module.parse_modules(ZEPHYR_BASE, self.manifest):
|
