Searched full:manifest (Results 1 – 25 of 42) sorted by relevance
12
| /Zephyr-Core-2.7.6/doc/guides/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 | 16 - The manifest file parser was incorrectly allowing project names which contain
25 - The changes made in west v0.10.1 to the ``west init --manifest-rev`` option
26 which selected the default branch name were leaving the manifest repository
41 ``west init --manifest-rev`` option value, if given, must now be either a
44 request can no longer be passed to ``--manifest-rev``. Users must now fetch
49 - ``west.manifest.Manifest.get_projects()`` avoids incorrect results in
52 - ``west.manifest.Project.sha()`` now works correctly for tag revisions.
75 avoids issues if the URL changes in the manifest file from when the submodule
81 - the :ref:`west-apis-manifest` module has fixed docstrings for the Project
89 - The :ref:`west-init` command's ``--manifest-rev`` (``--mr``) option no longer
[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 | 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 | 77 .. py:attribute:: manifest
79 A property which returns the :py:class:`west.manifest.Manifest`
80 instance for the current manifest file or aborts the program if one was
89 True if reading the manifest property will succeed instead of erroring
222 .. _west-apis-manifest:
224 west.manifest
227 .. automodule:: west.manifest
229 The main classes are `Manifest` and `Project`. These represent the contents of
230 a :ref:`manifest file <west-manifests>`. The recommended methods for parsing
231 west manifests are `Manifest.from_file` and `Manifest.from_data`.
[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:
|
| D | west-not-found.rst | 8 .. _west-apis-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',
|
| D | without-west.rst | 35 :term:`west manifest` file inside that repository.
98 [manifest]
|
| /Zephyr-Core-2.7.6/.github/workflows/ |
| D | manifest.yml | 1 name: Manifest
10 name: Manifest
20 - name: Manifest
21 uses: zephyrproject-rtos/action-manifest@2f1ad2908599d4fe747f886f9d733dd7eebae4ef
24 manifest-path: 'west.yml'
26 label-prefix: 'manifest-'
28 labels: 'manifest, west'
|
| /Zephyr-Core-2.7.6/doc/_extensions/zephyr/ |
| D | link-roles.py | 13 import west.manifest
15 west_manifest = west.manifest.Manifest.from_file()
34 # Try to get the zephyr repository's GitHub URL from the manifest.
44 # If zephyr is the manifest repository, this raises
|
| /Zephyr-Core-2.7.6/soc/xtensa/intel_adsp/common/bootloader/ |
| D | base_module.c | 9 #include "manifest.h"
13 * Each module has an entry in the FW manifest header. This is NOT part of
15 * for parsing by rimage (to genrate the manifest).
|
| D | boot_module.c | 9 #include "manifest.h"
13 * Each module has an entry in the FW manifest header. This is NOT part of
15 * for parsing by rimage (to generate the manifest).
|
| D | manifest.h | 17 /* FW Extended Manifest Header id = $AE1 */
106 * FW Manifest Header
143 * Firmware manifest descriptor. This can contain N modules and N module
185 * Module Manifest for rimage module metadata. Not used by ROM.
193 * Module offset in manifest.
|
| D | boot_loader.c | 19 #include "manifest.h"
140 /* Calculate fw size passed in BASEFW module in MANIFEST */ in get_fw_size_in_use()
161 /* parse FW manifest and copy modules */
346 /* parse manifest and copy modules */ in boot_master_core()
|
| /Zephyr-Core-2.7.6/doc/ |
| D | glossary.rst | 77 west manifest
83 west manifest repository
85 :term:`west manifest`. Its location is given by the :ref:`manifest.path
90 a :term:`west manifest repository`. You clone the Zephyr source
|
| /Zephyr-Core-2.7.6/ |
| 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:
|
| /Zephyr-Core-2.7.6/scripts/ |
| D | zephyr_module.py | 253 from west.manifest import Manifest
258 manifest = Manifest.from_file()
260 projects = [p.posixpath for p in manifest.get_projects([])
261 if manifest.is_active(p)]
263 projects = [p.posixpath for p in manifest.get_projects([])]
384 # and/or the west manifest file.
|
| /Zephyr-Core-2.7.6/modules/ |
| D | Kconfig | 8 comment "Optional modules. Make sure they're installed, via the project manifest."
36 comment "Unavailable modules, please install those via the project manifest."
|
| /Zephyr-Core-2.7.6/boards/xtensa/intel_adsp_cavs15/tools/ |
| D | flash.sh | 16 west sign -d ${BUILD} -t rimage -p $4 -D $3 -- -k $2 --no-manifest
|
| /Zephyr-Core-2.7.6/soc/xtensa/intel_adsp/cavs_v15/include/soc/ |
| D | memory.h | 123 /* Manifest base address in IMR - used by boot loader copy procedure. */
126 /* Manifest size (seems unused). */
|
| /Zephyr-Core-2.7.6/soc/xtensa/intel_adsp/cavs_v18/include/soc/ |
| D | memory.h | 120 /* Manifest base address in IMR - used by boot loader copy procedure. */
123 /* Manifest size (seems unused). */
|
| /Zephyr-Core-2.7.6/soc/xtensa/intel_adsp/cavs_v20/include/soc/ |
| D | memory.h | 120 /* Manifest base address in IMR - used by boot loader copy procedure. */
123 /* Manifest size (seems unused). */
|
12
