Searched full:manifest (Results 1 – 25 of 83) sorted by relevance
1234
7 manifest files, and the ``west manifest`` command. For API documentation on the8 ``west.manifest`` module, see :ref:`west-apis-manifest`. For a more general32 The history of the manifest repository is the line of Git commits which is39 The commits in the manifest repository (again, for upstream Zephyr this is the40 zephyr repository itself) each have a manifest file. The manifest file in each43 diagram. Each dotted line arrow points from a commit in the manifest repository48 - Projects can be added (like ``P1`` between manifest repository50 manifest repository commits)52 - Project and manifest repository histories don't have to move67 the same time": every manifest file refers to exactly one commit in[all …]
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 when20 warnings. These warnings are errors if the new ``manifest.project-filter``41 - ``west.manifest.Manifest.is_active()`` now respects the42 ``manifest.project-filter`` configuration option's value.49 - Manifest schema version "1.0" is now available for use in this release. This51 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.[all …]
24 │ # The manifest repository, never modified by west after creation:26 │ ├── west.yml # manifest file63 manifest repository64 Every west workspace contains exactly one *manifest repository*, which is a65 Git repository containing a *manifest file*. The location of the manifest66 repository is given by the :ref:`manifest.path configuration option69 For upstream Zephyr, :file:`zephyr` is the manifest repository, but you can70 configure west to use any Git repository in the workspace as the manifest71 repository. The only requirement is that it contains a valid manifest file.73 :ref:`west-manifests` for details on the manifest file format.[all …]
14 names as specified in the manifest file, or (as a fallback) paths to them17 to using all projects in the manifest file plus the manifest repository29 1. Cloning a new manifest repository from a remote URL30 2. Creating a workspace around an existing local manifest repository32 **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 using41 the location of the manifest file within the repository using ``--mf``.51 :file:`zp/.west`, and set the ``manifest.path`` :ref:`configuration option52 <west-config>` to ``zephyr`` to record the location of the manifest53 repository in the workspace. The default manifest file location is used.[all …]
9 .. _west-manifest-rev:11 The ``manifest-rev`` branch14 West creates and controls a Git branch named ``manifest-rev`` in each15 project. This branch points to the revision that the manifest file17 Other workspace management commands may use ``manifest-rev`` as a reference19 purposes, the ``manifest-rev`` branch allows the manifest file to use SHAs22 Although ``manifest-rev`` is a normal Git branch, west will recreate and/or27 rebase it on top of a new ``manifest-rev``, or merge ``manifest-rev`` into32 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 …]
18 [manifest]24 Above, the ``manifest`` section has option ``path`` set to ``zephyr``. Another25 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-manifest78 :term:`west manifest` inside the :file:`some-other-manifest` directory89 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 using99 the directory in the upstream manifest by running ``west config zephyr.base138 * - ``manifest.file``[all …]
69 .. py:attribute:: manifest71 A property which returns the :py:class:`west.manifest.Manifest`72 instance for the current manifest file or aborts the program if one was81 True if reading the manifest property will succeed instead of erroring305 .. _west-apis-manifest:307 west.manifest310 .. automodule:: west.manifest312 The main classes are :py:class:`Manifest` and :py:class:`Project`. These313 represent the contents of a :ref:`manifest file <west-manifests>`. The315 :py:meth:`Manifest.from_topdir`.[all …]
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 untrusted207 Step 3: Update Your Manifest211 just edited in your west manifest. If your extension is in a project, add it216 manifest:228 Alternatively, if your extension is in the manifest repository, just do the229 same thing in the manifest's ``self`` section, like this:233 manifest:
2 Manifest Revisions Table6 present in a manifest file.11 This extension introduces a new directive: ``manifest-projects-table``. It can14 .. manifest-projects-table::22 - ``manifest_projects_table_manifest``: Path to the manifest file.36 from west.manifest import Manifest43 """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 …]
14 import west.manifest17 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
1 name: Manifest8 name: Manifest28 - name: Manifest29 uses: zephyrproject-rtos/action-manifest@v1.2.032 manifest-path: 'west.yml'35 label-prefix: 'manifest-'37 labels: 'manifest'
22 west config manifest.project-filter -- -hal_FOO25 .. manifest-projects-table::39 west config manifest.project-filter -- +nanopb42 .. manifest-projects-table::50 default manifest.51 To use any of the projects below, you will need to define your own manifest52 file which includes them. See :ref:`west-manifest-import` for information on
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 …]
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 …]
1 This directory can contain additional west manifest files. Any files10 …://docs.zephyrproject.org/latest/guides/west/manifest.html#example-2-2-downstream-with-directory-o…
1 # Example manifest file you can include into the main west.yml file.14 manifest:
12 /* OpenTitan manifest consists of 896 bytes (224 words) containing signature,14 * except for entry point (final word in manifest).20 /* Entry point is relative to the beginning of manifest. */
7 """Script to pack EC binary with manifest header.10 image with a manifest header, ISH shim loader will parse this header and load38 """Returns a binary blob that represents a manifest entry"""68 # Add manifest for main ISH binary74 # Add manifest for aontask binary79 # Add manifest that signals end of manifests
100 west manifest106 west manifest repository108 :term:`west manifest`. Its location is given by the :ref:`manifest.path113 a :term:`west manifest repository`. You clone the Zephyr source
455 from west.manifest import MANIFEST_REV_BRANCH459 # Special treatment of manifest project.478 meta.update({'west': {'manifest': west_projs['manifest_path'],517 def west_projects(manifest = None): argument524 from west.manifest import Manifest532 # west.manifest.MalformedConfig until west v0.14.0, for example.534 from west.manifest import \542 if not manifest:543 manifest = Manifest.from_file()545 projects = [p for p in manifest.get_projects([])[all …]
4 #include <manifest.h>9 * SOF with IPC3, but instead are inserted to *MANIFEST* of the final16 * module UUID in manifest must be identical with the one in firmware code,
1 # The west manifest file for upstream Zephyr.4 # path to the project containing this file in the [manifest] section's7 # You are free to create your own manifest files and put them in any9 # For example, you could create a manifest file in your own out of13 # You can pass your manifest repositories to west init when creating a17 manifest:36 repo-path: babblesim-manifest
106 Integration in main manifest file (west.yaml)109 Integrating external code into the main :file:`west.yml` manifest file is125 platform shall be added to an optional manifest file that is filtered by144 Zephyr project manifest with documentation instructing users and developers how227 project in the main :file:`west.yml` manifest. Therefore, this section does not247 :file:`west.yml` manifest. More info on optional projects can be found in248 :ref:`this section <west-manifest-groups>`.254 Additional considerations about the main manifest258 the `main manifest file`_ requires TSC approval. This includes, but is not265 .. _main manifest file:
17 /* FW Extended Manifest Header id = $AE1 */107 * FW Manifest Header144 * Firmware manifest descriptor. This can contain N modules and N module187 * Module Manifest for rimage module metadata. Not used by ROM.
... thumbnail.png meta.xml META-INF/manifest
