Searched full:projects (Results 1 – 25 of 145) sorted by relevance
123456
| /Zephyr-latest/doc/develop/manifest/ |
| D | index.rst | 5 West Projects index
11 Active Projects/Modules
14 The projects below are enabled by default and will be downloaded when you
15 call :command:`west update`. Many of the projects or modules listed below are
25 .. manifest-projects-table::
28 Inactive and Optional Projects/Modules
32 The projects below are optional and will not be downloaded when you
33 call :command:`west update`. You can add any of the projects or modules listed below
42 .. manifest-projects-table::
45 External Projects/Modules
[all …]
|
| /Zephyr-latest/doc/develop/west/ |
| D | basics.rst | 9 West's built-in commands allow you to work with :term:`projects <west project>`
15 :term:`projects <west project>` listed in the manifest in the workspace.
35 │ # Projects managed by west:
41 └── [ ... other projects ...]
83 The manifest file is a YAML file that defines *projects*, which are the
89 workspace's projects based on the contents of the manifest file.
91 projects
92 Projects are Git repositories managed by west. Projects are defined in the
94 example workspace, ``zcbor`` and ``net-tools`` are projects.
97 the locations of all the projects in the workspace, so any code they contain
[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 | 49 ``projects:`` element. See :ref:`west-manifests-projects` for examples.
342 - ``west status`` now only prints output for projects which have a nonempty
354 :ref:`west-manifests-projects` for examples.
405 - ``west update`` now synchronizes Git submodules in projects by default. This
502 enabled and disabled to determine what projects are "active", and therefore
506 - ``west update`` no longer updates inactive projects by default. It now
511 with no arguments does not print information for inactive projects by
512 default. If the user specifies a list of projects explicitly at the command
516 projects, even inactive ones.
704 commands can operate on multiple projects; if a subprocess related to one
[all …]
|
| /Zephyr-latest/doc/_extensions/zephyr/ |
| D | manifest_projects_table.py | 5 This extension allows to render a table containing the revisions of the projects
11 This extension introduces a new directive: ``manifest-projects-table``. It can
14 .. manifest-projects-table::
73 projects = []
74 for project in manifest.projects:
85 projects.append(project)
109 for project in projects:
137 directives.register_directive("manifest-projects-table", ManifestProjectsTable)
|
| D | link-roles.py | 98 projects = [p.name for p in west_manifest.projects] if west_manifest else []
99 if module in projects:
|
| /Zephyr-latest/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
543 projects = [ prj for prj in meta_projects_list[1:] if prj["path"] == project_path ]
545 return projects[0] if len(projects) == 1 else None
550 # Process zephyr_base, projects, and modules and create a dictionary
556 # - west-projects: path and revision
577 projects = west_projs['projects']
580 manifest_path = projects[0].posixpath
597 elif not [ prj for prj in projects[1:] if prj.posixpath == manifest_path ]:
599 projects[0].posixpath)
[all …]
|
| /Zephyr-latest/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-latest/scripts/west_commands/completion/ |
| D | west-completion.fish | 134 # return the list of projects
138 set -l projects
150 set projects (west "-z $zephyr_base" list --format="{name}")
152 set projects (west list --format="{name}")
155 printf "%s\n" $projects
161 "update" "update projects described in west manifest" \
162 "list" "print information about projects" \
164 "diff" '"git diff" for one or more projects' \
165 "status" '"git status" for one or more projects' \
166 "forall" "run a command in one or more local projects" \
[all …]
|
| 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]'
147 {-a,--all}'[include inactive projects]'
170 {-a,--all}'[include inactive projects]'
179 {-a,--all}'[include inactive projects]'
189 {-a,--all}'[include inactive projects]'
|
| /Zephyr-latest/cmake/sca/eclair/ |
| D | sca_options.cmake | 3 option(ECLAIR_RULESET_FIRST_ANALYSIS "A tiny selection of the projects coding guideline rules to
6 option(ECLAIR_RULESET_STU "Selection of the projects coding guidelines, which can be verified
|
| /Zephyr-latest/doc/templates/ |
| D | sample.tmpl | 19 [For simple projects, a description of how to wire the board for the demo. For
20 complex projects, provide a graphic with more details, preferably using
|
| /Zephyr-latest/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
122 Standalone or loose integration of modules/projects without any incoming
124 projects that provide value to users directly and through a Zephyr subsystem or
128 Such optional projects might include samples and tests in their own repositories.
240 :ref:`modules-vs-projects` for additional information on the differences.
247 :file:`west.yml` manifest. More info on optional projects can be found in
257 In general, any additions or removals whatsoever to the ``projects:`` section of
262 - Adding and removing projects
|
| /Zephyr-latest/doc/ |
| D | glossary.rst | 166 A YAML file, usually named :file:`west.yml`, which describes projects, or
180 is different from a :term:`zephyr module`, although many projects are also
181 modules. See :ref:`west-manifests-projects` for additional information.
186 as well as that of its :term:`west projects <west project>` onto your
199 projects, but they do not have to. See :ref:`modules` for additional
|
| /Zephyr-latest/submanifests/ |
| D | example.yaml.sample | 15 projects:
|
| D | optional.yaml | 6 projects:
|
| /Zephyr-latest/samples/ |
| D | index.rst | 8 own projects.
|
| /Zephyr-latest/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]
|
| /Zephyr-latest/drivers/timer/ |
| D | Kconfig.cavs | 8 # symbiotic relationship between these two projects, that from
|
| /Zephyr-latest/ |
| D | README.rst | 13 …/bestpractices.coreinfrastructure.org/projects/74"><img src="https://bestpractices.coreinfrastruct…
14 …zephyrproject-rtos/zephyr"><img src="https://api.securityscorecards.dev/projects/github.com/zephyr…
|
| /Zephyr-latest/scripts/dts/ |
| D | README.txt | 10 projects.
|
| /Zephyr-latest/boards/altr/max10/doc/ |
| D | index.rst | 219 Reading symbols from /projects/zephyr/samples/hello_world/build/zephyr/zephyr.elf...done.
224 isr_tables_syms () at /projects/zephyr/arch/common/isr_tables.c:63
227 Breakpoint 1 at 0xdf0: file /projects/zephyr/arch/nios2/core/prep_c.c, line 36.
229 Breakpoint 2 at 0x1254: file /projects/zephyr/kernel/init.c, line 348.
233 Breakpoint 2, z_cstart () at /projects/zephyr/kernel/init.c:348
|
| /Zephyr-latest/scripts/pylint/checkers/ |
| D | argparse-checker.py | 23 "abbreviations and prevent issues with these being used by projects"
|
123456
