Searched full:projects (Results 1 – 25 of 87) sorted by relevance
1234
| /Zephyr-Core-3.4.0/doc/develop/west/ |
| D | basics.rst | 9 West's built-in commands allow you to work with *projects* (Git
29 │ # Projects managed by west:
34 └── [ ... other projects ...]
76 The manifest file is a YAML file that defines *projects*, which are the
82 workspace's projects based on the contents of the manifest file.
84 projects
85 Projects are Git repositories managed by west. Projects are defined in the
87 example workspace, ``zcbor`` and ``net-tools`` are projects.
90 the locations of all the projects in the workspace, so any code they contain
91 can be used as :ref:`modules`. Note however that modules and projects
[all …]
|
| D | manifest.rst | 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:
[all …]
|
| D | built-in.rst | 13 Some commands take projects as arguments. These arguments can be project
17 to using all projects in the manifest file plus the manifest repository
91 **Which projects are updated:**
96 only the active projects are updated.
98 To operate on a subset of projects only, give ``PROJECT`` argument(s). Each
101 projects explicitly, they are updated regardless of whether they are active.
157 ``west update --rebase`` will fail in projects that have git conflicts
168 never fails either but does not treat all projects the same:
170 - in projects where your branch diverged from the incoming commits, it
173 - in all other projects where no rebase or merge is needed it keeps
[all …]
|
| D | workspaces.rst | 81 To use this helper on just the projects ``foo`` and ``bar``, run:
139 Projects can be located anywhere inside the workspace, but they may not
144 projects must have paths inside the workspace.
178 and names other projects required to build it in its :file:`west.yml`. This
181 the super-project, zephyr and other projects as submodules
216 projects:
240 projects:
256 imported projects separately. In the above example, using ``import`` means
267 and specifies a list of projects all at the same "level"
298 v2.5.0 and its modules, then add the ``app1`` and ``app2`` projects:
[all …]
|
| D | release-notes.rst | 267 - ``west status`` now only prints output for projects which have a nonempty
279 :ref:`west-manifests-projects` for examples.
330 - ``west update`` now synchronizes Git submodules in projects by default. This
427 enabled and disabled to determine what projects are "active", and therefore
431 - ``west update`` no longer updates inactive projects by default. It now
436 with no arguments does not print information for inactive projects by
437 default. If the user specifies a list of projects explicitly at the command
441 projects, even inactive ones.
629 commands can operate on multiple projects; if a subprocess related to one
631 projects. All of them also now report a nonzero error code from the west
[all …]
|
| /Zephyr-Core-3.4.0/scripts/ |
| D | zephyr_module.py | 7 '''Tool for parsing a list of projects to determine if they are Zephyr
8 projects. If no projects are given then the output from `west list` will be
404 # Process zephyr_base, projects, and modules and create a dictionary
410 # - west-projects: path and revision
456 projects = west_projs['projects']
460 manifest_proj_path = PurePath(projects[0].posixpath).as_posix()
467 for project in projects[1:]:
479 'projects': meta_projects}})
519 projects = []
526 # West is not installed, so don't return any projects.
[all …]
|
| /Zephyr-Core-3.4.0/doc/build/ |
| D | zephyr_cmake_package.rst | 107 <projects>/zephyr-workspace/zephyr
111 in this example, ``hello_world`` will use ``<projects>/zephyr-workspace/zephyr``.
119 <projects>/zephyr-workspace
125 in this example, ``my_first_app`` will use ``<projects>/zephyr-workspace/zephyr`` as this Zephyr
137 <projects>/zephyr-workspace-1
140 <projects>/zephyr-workspace-2
149 in this example, only ``<projects>/zephyr-workspace-2/zephyr`` is exported to the CMake package
153 If user wants to test the application with ``<projects>/zephyr-workspace-1/zephyr``, this can be
155 ``ZEPHYR_BASE=<projects>/zephyr-workspace-1/zephyr``, before
195 <projects>/zephyr-workspace-2.a
[all …]
|
| /Zephyr-Core-3.4.0/doc/templates/ |
| D | sample.tmpl | 17 [For simple projects, a description of how to wire the board for the demo. For
18 complex projects, provide a graphic with more details, preferably using
|
| /Zephyr-Core-3.4.0/doc/_extensions/zephyr/ |
| D | link-roles.py | 79 projects = [p.name for p in west_manifest.projects] if west_manifest else []
80 if module in projects:
|
| /Zephyr-Core-3.4.0/scripts/west_commands/completion/ |
| D | west-completion.zsh | 14 'update[update projects described in west manifest]'
15 'list[print information about projects]'
17 'diff["git diff" for one or more projects]'
18 'status["git status" for one or more projects]'
19 'forall[run a command in one or more local projects]'
139 {-a,--all}'[include inactive projects]'
162 {-a,--all}'[include inactive projects]'
171 {-a,--all}'[include inactive projects]'
181 {-a,--all}'[include inactive projects]'
|
| /Zephyr-Core-3.4.0/doc/contribute/ |
| D | external.rst | 8 available in other open source projects.
31 Integrating code into the Zephyr Project from other projects that use a license
198 :ref:`modules-vs-projects` for additional information on the differences.
205 :file:`west.yml` manifest. More info on optional projects can be found in
215 In general, any additions or removals whatsoever to the ``projects:`` section of
220 - Adding and removing projects
|
| /Zephyr-Core-3.4.0/submanifests/ |
| D | example.yaml.sample | 15 projects:
|
| /Zephyr-Core-3.4.0/scripts/west_commands/zspdx/ |
| D | cmakefileapijson.py | 113 projects_arr = cfg_dict.get("projects", [])
122 cfg.projects.append(prj)
344 for cfgPrj in cfg.projects:
360 cfgDir.project = cfg.projects[cfgDir.projectIndex]
376 cfgPrj.parent = cfg.projects[cfgPrj.parentIndex]
380 cfgPrj.children.append(cfg.projects[childIndex])
401 cfgTarget.project = cfg.projects[cfgTarget.projectIndex]
|
| D | cmakefileapi.py | 27 self.projects = []
60 # A member of the configuration.projects array
|
| /Zephyr-Core-3.4.0/drivers/timer/ |
| D | Kconfig.cavs | 8 # symbiotic relationship between these two projects, that from
|
| /Zephyr-Core-3.4.0/samples/net/cloud/google_iot_mqtt/ |
| D | prj.conf | 61 CONFIG_CLOUD_CLIENT_ID="projects/<PROJECT_ID>/locations/<REGION>/registries/<REGISTRY_ID>/devices/<…
|
| D | README.rst | 58 CLOUD_CLIENT_ID="projects/PROJECT_ID/locations/REGION/registries/REGISTRY_ID/devices/DEVICE_ID"
|
| /Zephyr-Core-3.4.0/scripts/dts/ |
| D | README.txt | 10 projects.
|
| /Zephyr-Core-3.4.0/doc/develop/ |
| D | modules.rst | 3 Modules (External projects)
6 Zephyr relies on the source code of several externally maintained projects in
41 .. _modules-vs-projects:
43 Modules vs west projects
46 Zephyr modules, described in this page, are not the same as :ref:`west projects
55 :ref:`West projects <west-manifests-projects>` are entries in the `projects:`
57 West projects are often also modules, but not always. There are west projects
64 The contents of this page only apply to modules, and not to west projects in
79 tracking external projects (hosted in Git repositories); such modules
386 Certain external projects provide test suites that reside in the upstream
[all …]
|
| /Zephyr-Core-3.4.0/boards/nios2/altera_max10/doc/ |
| D | index.rst | 229 Reading symbols from /projects/zephyr/samples/hello_world/build/zephyr/zephyr.elf...done.
234 isr_tables_syms () at /projects/zephyr/arch/common/isr_tables.c:63
237 Breakpoint 1 at 0xdf0: file /projects/zephyr/arch/nios2/core/prep_c.c, line 36.
239 Breakpoint 2 at 0x1254: file /projects/zephyr/kernel/init.c, line 348.
243 Breakpoint 2, _Cstart () at /projects/zephyr/kernel/init.c:348
|
| /Zephyr-Core-3.4.0/.github/ISSUE_TEMPLATE/ |
| D | 003_rfc-proposal.md | 42 modifications in other areas), or other teams/projects.
|
| /Zephyr-Core-3.4.0/scripts/pylint/checkers/ |
| D | argparse-checker.py | 23 "abbreviations and prevent issues with these being used by projects"
|
| /Zephyr-Core-3.4.0/ |
| D | README.rst | 13 <a href="https://bestpractices.coreinfrastructure.org/projects/74"><img
14 src="https://bestpractices.coreinfrastructure.org/projects/74/badge"></a>
|
| /Zephyr-Core-3.4.0/doc/services/tfm/ |
| D | requirements.rst | 79 `SRecord for Windows <https://sourceforge.net/projects/srecord/files/srecord-win32>`_
|
| /Zephyr-Core-3.4.0/doc/develop/languages/c/ |
| D | minimal_libc.rst | 11 It is very low footprint and is suitable for projects that do not rely on less
|
1234
