Lines Matching full:projects
48 - Projects can be added (like ``P1`` between manifest repository
68 the projects it cares about. This can be relaxed by using a branch
85 projects:
86 # a list of projects managed by west
101 ``projects``, and ``self``. In YAML terms, the value of the ``manifest`` key is
105 The ``projects`` value is a list of repositories managed by west and associated
107 section, which can be used to save typing in the ``projects`` list.
113 where projects can be fetched from.
118 below, projects can also specify their complete fetch URLs.)
154 .. _west-manifests-projects:
156 Projects subsection
159 The ``projects`` subsection contains a sequence describing the project
161 specify what Git remote URLs to use when cloning and fetching the projects,
163 file system. Note that west projects :ref:`are different from modules
164 <modules-vs-projects>`.
175 projects:
224 .. list-table:: projects elements keys
257 Projects may not have both ``url`` and ``repo-path`` attributes.
290 - Optional. If ``true``, imports projects from manifest files in the
340 projects:
418 - Optional. This is also analogous to the ``projects`` key, but allows
419 importing projects from other files in the manifest repository. See
482 - ``submodules:`` in ``projects:`` (:ref:`west-manifest-submodules`)
483 - ``manifest: group-filter:``, and ``groups:`` in ``projects:``
493 - Support for ``userdata:`` in ``projects:`` (:ref:`west-project-userdata`)
503 - Support for ``description:`` in ``projects:``
504 (:ref:`west-manifests-projects`)
528 .. _west-active-inactive-projects:
530 Active and Inactive Projects
533 Projects defined in the west manifest can be *inactive* or *active*. The
535 example, ``west update`` will not update inactive projects, and ``west list``
560 :ref:`above <west-manifest-files>` to place projects into groups, and to
563 For example, this lets you run a ``west forall`` command only on the projects
565 projects inactive; see the previous section for more information on inactive
566 projects.
582 projects:
589 You can enable or disable project groups using ``group-filter``. Projects whose
598 projects:
608 The projects are in these groups:
690 projects. The examples use both ``manifest: group-filter:`` YAML lists and
709 projects:
729 all three projects (``foo``, ``bar``, and ``baz``) are active. Note that there
740 projects:
771 projects:
802 projects:
834 projects:
859 Therefore, projects ``foo`` and ``bar`` are both active.
869 projects:
894 Therefore, projects ``foo`` and ``bar`` are both active.
904 projects:
926 Therefore, projects ``foo`` and ``bar`` are both inactive.
962 projects:
978 projects:
1005 projects:
1021 projects:
1031 Only the ``child``, ``project-1``, and ``project-3`` projects are active.
1052 projects:
1068 projects:
1084 Then only the ``child``, ``project-1``, and ``project-3`` projects are active.
1099 Git Submodules in Projects
1105 appear inside ``projects``, like this:
1110 projects:
1122 If ``submodules`` is ``true`` as a ``projects`` attribute, ``west update`` will
1135 projects:
1167 projects:
1184 West versions v0.12 and later support an optional ``userdata`` key in projects.
1201 projects:
1229 You can use the ``import`` key briefly described above to include projects from
1236 projects:
1250 #. imported files in ``projects``
1252 During resolution, west ignores projects which have already been defined in
1254 makes west ignore other projects named ``foo`` imported from your ``projects``
1294 If ``import`` is ``true`` as a ``projects`` attribute, west imports projects
1303 projects:
1341 ├── [ ... other projects ...] # other mainline repositories
1355 projects:
1372 After ``west update``, all of the projects defined in the ``zephyr``
1394 projects:
1414 be used to import projects from Zephyr. This lets you stay up to date with the
1447 projects:
1455 import: true # imported projects have lower precedence
1464 projects:
1490 - locally check out the ``v2.0.0`` revisions for all zephyr projects except
1501 of the ``projects`` or ``self`` repository the ``import`` key appears in.
1508 projects:
1528 Notice how ``projects`` imports get data from Git using ``manifest-rev``, while
1546 projects:
1577 manifest file, :file:`my-repo/west.yml`, in addition to projects in
1590 projects:
1616 in the ``self`` section is processed before the manifest files in ``projects``
1619 This means projects defined in :file:`my-repo/submanifests` take highest
1624 This may seem strange, but it allows you to redefine projects "after the fact",
1643 projects:
1652 :file:`my-repo/submanifests`. The projects defined in :file:`00-ci.yml` have
1657 projects named ``a-vendor-hal`` and ``an-application``, even if those same
1658 projects are also defined elsewhere.
1681 projects. This can be used to place these projects in a subdirectory of the
1698 projects, however. We'll assume the mainline :file:`west.yml` is
1705 projects:
1718 projects:
1736 projects:
1766 projects:
1779 projects:
1795 projects:
1828 projects:
1843 projects:
1862 projects:
1879 You want to import a manifest and its projects, placing everything into a
1883 adding this project and its projects ``bar`` and ``baz`` to your workspace:
1894 projects:
1914 projects:
1931 projects:
1959 projects:
1981 projects:
2002 #. :file:`my-repo/west.yml` is next (with projects ``my-library`` etc. as long
2005 in the ``projects`` list in :file:`my-repo/west.yml`
2020 The ``import`` key can appear in a west manifest's ``projects`` and ``self``
2027 projects:
2049 - a ``projects`` list, which is produced by combining the ``projects`` defined
2079 Projects subsubsection
2082 This section describes how the final ``projects`` list is created.
2084 Projects are identified by name. If the same name occurs in multiple manifests,
2091 from Git at the latest ``manifest-rev`` revisions in their projects. These
2112 extra projects shouldn't take too much time unless it's really needed. See the
2191 projects are handled during manifest resolution, set the maximum verbosity