| /Zephyr-Core-3.7.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 | release-notes.rst | 48 - The manifest file format now supports a ``description`` field in each
55 :ref:`west-manifest-rev`.
75 - ``west.manifest.Project`` now has a ``description`` attribute,
77 in the manifest data.
87 workspace against the manifest.
89 - Support for a new ``manifest.project-filter`` configuration option.
90 See :ref:`west-config-index` for details. The ``west manifest --freeze``
91 and ``west manifest --resolve`` commands currently cannot be used when
95 warnings. These warnings are errors if the new ``manifest.project-filter``
116 - ``west.manifest.Manifest.is_active()`` now respects the
[all …]
|
| D | basics.rst | 13 :term:`west workspace`, and clones the :term:`manifest repo <west manifest
15 :term:`projects <west project>` listed in the manifest in the workspace.
30 │ # The manifest repository, never modified by west after creation:
32 │ ├── west.yml # manifest file
69 manifest repository
70 Every west workspace contains exactly one *manifest repository*, which is a
71 Git repository containing a *manifest file*. The location of the manifest
72 repository is given by the :ref:`manifest.path configuration option
75 For upstream Zephyr, :file:`zephyr` is the manifest repository, but you can
76 configure west to use any Git repository in the workspace as the manifest
[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 | 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
156 * - ``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
338 .. _west-apis-manifest:
340 west.manifest
343 .. automodule:: west.manifest
345 The main classes are :py:class:`Manifest` and :py:class:`Project`. These
346 represent the contents of a :ref:`manifest file <west-manifests>`. The
348 :py:meth:`Manifest.from_topdir`.
[all …]
|
| 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
207 Step 3: Update Your Manifest
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:
|
| /Zephyr-Core-3.7.0/doc/_extensions/zephyr/ |
| D | manifest_projects_table.py | 2 Manifest Revisions Table
6 present in a manifest file.
11 This extension introduces a new directive: ``manifest-projects-table``. It can
14 .. manifest-projects-table::
22 - ``manifest_projects_table_manifest``: Path to the manifest file.
36 from west.manifest import Manifest
43 """Manifest revisions table."""
73 manifest = Manifest.from_file(self.env.config.manifest_projects_table_manifest)
75 for project in manifest.projects:
76 if project.name == "manifest":
[all …]
|
| D | link-roles.py | 14 import west.manifest
17 west_manifest = west.manifest.Manifest.from_file()
73 # Try to get a module repository's GitHub URL from the manifest.
92 f"Module {module} not found in the west manifest\n\t{trace}"
94 # Baseurl for manifest project not set
|
| /Zephyr-Core-3.7.0/.github/workflows/ |
| D | manifest.yml | 1 name: Manifest
8 name: Manifest
28 - name: Manifest
29 uses: zephyrproject-rtos/action-manifest@v1.3.1
32 manifest-path: 'west.yml'
36 label-prefix: 'manifest-'
38 labels: 'manifest'
|
| /Zephyr-Core-3.7.0/soc/lowrisc/opentitan/ |
| D | rom_header.S | 12 /* OpenTitan manifest consists of 1024 bytes (256 words) of manifest
16 * The layout below conforms to manifest version: 0x71c3 (major),
17 * 0x6c47 (minor). The manifest format is documented here:
18 …titan/blob/689a163294e1791bd30cfe096decf7f9233abad4/sw/host/opentitanlib/src/image/manifest.rs#L205
24 /* Entry point is relative to the beginning of manifest. */
|
| /Zephyr-Core-3.7.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
56 Use the template :file:`doc/develop/manifest/external/external.rst.tmpl` to add
|
| /Zephyr-Core-3.7.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.7.0/scripts/west_commands/completion/ |
| D | west-completion.zsh | 14 'update[update projects described in west manifest]'
16 'manifest[manage the west manifest]'
118 '(-l --local)'{--mr,--manifest-rev}'[manifest revision]:manifest rev:'
119 {--mf,--manifest-file}'[manifest file]:manifest file:'
120 '(-l --local)'{-m,--manifest}'[manifest URL]:manifest URL:_directories'
121 …'(-m --manifest --mr --manifest-rev)'{-l,--local}'[use local directory as manifest repository]:loc…
136 {-k,--keep-descendants}'[keep manifest-rev descendants checked out]'
137 {-r,--rebase}'[rebase checked out branch onto the new manifest-rev]'
147 '--manifest-path-from-yaml[print performance stats]'
157 '--resolve[resolve into single manifest]'
[all …]
|
| D | west-completion.fish | 161 "update" "update projects described in west manifest" \
163 "manifest" "manage the west manifest" \
241 if string match -rq '^\s*\[manifest\]\s*$' $line
290 # if the manifest folder is not a git repo, use the hash of the manifest file
347 …and_from init; and __zephyr_west_exclude -l --local" -l mr -l manifest-rev -r -d "manifest revisio…
348 …e -c west -n "__zephyr_west_seen_subcommand_from init" -l mf -l manifest-file -r -d "manifest file"
349 …d __zephyr_west_exclude -l --local" -o m -l manifest -ra "(__zephyr_west_complete_directories)" -d…
350 …t_exclude -m --manifest --mr --manifest-rev" -o l -l local -ra "(__zephyr_west_complete_directorie…
353 … -c west -n __zephyr_west_use_subcommand -ra update -d "update projects described in west manifest"
361 …hyr_west_seen_subcommand_from update" -o k -l keep-descendants -d "keep manifest-rev descendants c…
[all …]
|
| /Zephyr-Core-3.7.0/soc/intel/intel_ish/utils/ |
| D | build_ish_firmware.py | 7 """Script to pack EC binary with manifest header.
10 image with a manifest header, ISH shim loader will parse this header and load
38 """Returns a binary blob that represents a manifest entry"""
68 # Add manifest for main ISH binary
74 # Add manifest for aontask binary
79 # Add manifest that signals end of manifests
|
| /Zephyr-Core-3.7.0/scripts/ |
| D | zephyr_module.py | 548 from west.manifest import MANIFEST_REV_BRANCH
554 # Special treatment of manifest project
555 # Git information (remote/revision) are not provided by west for the Manifest (west.yml)
556 …# To mitigate this, we check if we don't use the manifest from the zephyr repository or an other p…
581 # Iterates on all projects except the first one (manifest)
591 # Force manifest URL and set commit as 'off'
599 # If manifest is in project, updates related variables
605 meta.update({'west': {'manifest': west_projs['manifest_path'],
654 def west_projects(manifest=None): argument
661 from west.manifest import Manifest
[all …]
|
| /Zephyr-Core-3.7.0/soc/intel/intel_adsp/common/ |
| D | rimage_modules.c | 4 #include <manifest.h>
9 * SOF with IPC3, but instead are inserted to *MANIFEST* of the final
16 * module UUID in manifest must be identical with the one in firmware code,
|
| /Zephyr-Core-3.7.0/ |
| D | west.yml | 1 # The west manifest file for upstream Zephyr.
4 # path to the project containing this file in the [manifest] section's
7 # You are free to create your own manifest files and put them in any
9 # For example, you could create a manifest file in your own out of
13 # You can pass your manifest repositories to west init when creating a
17 manifest:
36 repo-path: babblesim-manifest
|
| /Zephyr-Core-3.7.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: argument
|
| /Zephyr-Core-3.7.0/doc/ |
| D | glossary.rst | 165 west manifest
171 west manifest repository
173 :term:`west manifest`. Its location is given by the :ref:`manifest.path
177 Each of the entries in a :term:`west manifest`, which describe a Git
179 corresponding :term:`west manifest repository`. Note that a west project
185 :term:`west manifest repository` in it. You clone the Zephyr source code,
|
| /Zephyr-Core-3.7.0/cmake/modules/ |
| D | FindBabbleSim.cmake | 16 # fetched babblesim using the manifest.
48 west config manifest.group-filter +babblesim && west update\n\
72 "If you got it from Zephyr's manifest, you can do:\n\
|
| /Zephyr-Core-3.7.0/soc/intel/intel_adsp/common/include/ |
| D | manifest.h | 17 /* FW Extended Manifest Header id = $AE1 */
107 * FW Manifest Header
144 * Firmware manifest descriptor. This can contain N modules and N module
187 * Module Manifest for rimage module metadata. Not used by ROM.
|
