| /Zephyr-latest/doc/_extensions/zephyr/ |
| D | manifest_projects_table.py | 74 for project in manifest.projects:
75 if project.name == "manifest":
79 and manifest.is_active(project)
81 and not manifest.is_active(project)
85 projects.append(project)
109 for project in projects:
114 entry += nodes.paragraph(text=project.name)
119 project.revision,
120 project.revision,
122 refuri=ManifestProjectsTable.rev_url(project.url, project.revision),
|
| /Zephyr-latest/tests/ztest/fail/ |
| D | CMakeLists.txt | 10 # Set the target binary for the 'core' external project. The path to this must match the one set
16 # Set the target binary for the 'core' external project. The path to this must match the one set
21 # Create the project and set the sources for the target
22 project(fail)
25 # Find which CONFIG_ZTEST_FAIL_TEST_* choice was set so we can pass it to the external project
27 # 'core' project as a cmake argument.
35 # Add the 'core' external project which will mirror the configs of this project.
|
| /Zephyr-latest/doc/project/ |
| D | proposals.rst | 37 importance to the project. Often, the requester may have a readiness and
47 the project goals and other timeline considerations. The priority is
59 by any project member or the community. You should contact an assigned owner if
66 Project roadmaps and release plans are both important tools for the project, but
67 they have very different purposes and should not be confused. A project roadmap
68 communicates the high-level overview of a project's strategy, while a release
72 - The project roadmap communicates the why; a release plan details the what
80 The project roadmap should serve as a high-level, visual summary of the
81 project's strategic objectives and expectations.
84 can help the project present its plan in a compelling way to existing and new
[all …]
|
| /Zephyr-latest/tests/arch/arm/arm_irq_vector_table/ |
| D | README.txt | 5 Verify a project can install ISRs directly in the vector table. Only for
12 This project outputs to the console. It can be built and executed on QEMU as
21 Problems caused by out-dated project information can be addressed by
22 issuing one of the following commands then rebuilding the project:
|
| /Zephyr-latest/doc/develop/west/ |
| D | built-in.rst | 13 Some commands take projects as arguments. These arguments can be project
15 on the local file system. Omitting project arguments to commands which
94 :file:`west.yml`, and updates each project specified there.
95 If your manifest uses :ref:`project groups <west-manifest-groups>`, then
99 ``PROJECT`` is either a project name as given in the manifest file, or a
100 path that points to the project within the workspace. If you specify
105 For each project that is updated, this command:
107 #. Initializes a local Git repository for the project in the workspace, if
109 #. Inspects the project's ``revision`` field in the manifest, and fetches
111 #. Sets the project's :ref:`manifest-rev <west-manifest-rev>` branch to the
[all …]
|
| D | manifest.rst | 35 repositories in the workspace, with each project repository boxed in by a
42 project repositories. This relationship is shown using dotted line arrows in the
44 to a corresponding commit in a project repository.
60 One use for moving backward in project history is to "revert" a regression by
66 - In the above diagram, no project repository has two revisions "at
84 # short names for project URLs
88 # default project attributes
94 # a list of project groups to enable or disable
116 the complete Git fetch URL for each project. A project's fetch URL can be set
117 by appending a project-specific path onto a remote URL base. (As we'll see
[all …]
|
| /Zephyr-latest/subsys/net/lib/http/ |
| D | README_http_parser | 4 The http-parser library* from the nodejs project is a downstream of an
5 externally maintained open source project. The original upstream code
14 * "http-parser" is the project's name, "http_parser" is used in filenames.
|
| /Zephyr-latest/tests/kernel/xip/ |
| D | README.txt | 11 This project outputs to the console. It can be built and executed
20 Problems caused by out-dated project information can be addressed by
21 issuing one of the following commands then rebuilding the project:
|
| /Zephyr-latest/doc/contribute/ |
| D | index.rst | 6 Contributions from the community are the backbone of the project. Whether it is by submitting code,
23 Learn about the overall process and guidelines for contributing to the Zephyr project.
26 how to ensure your contribution can be considered for inclusion in the project and potentially
31 contributors to the project.
42 project.
47 The Zephyr project thrives on good documentation. Whether it is as part of a code contribution or
48 as a standalone effort, contributing documentation is particularly valuable to the project.
89 blobs <blobs-process>` to the project.
94 When your first contribution to the Zephyr project gets merged, you'll become eligible to claim your
96 profile, etc. It will allow you to showcase your involvement in the Zephyr project and help raise
|
| D | external.rst | 34 `Zephyr project charter`_. The board will automatically reject licenses that
41 .. _Zephyr project charter:
56 comes from an existing project, there are additional questions that must be
60 into the project:
62 - Is this the most optimal way to introduce the functionality to the project?
65 - Is the external project being actively maintained? This is particularly
68 Are there other open source project that implement the same functionality?
80 The first way to integrate external source code into the project is to simply
86 - The code adheres to the project's :ref:`coding_guidelines`
99 The second way of integrating external source code into the project is to import
[all …]
|
| /Zephyr-latest/scripts/utils/ |
| D | twister_to_list.py | 47 def twister_to_list(project, dry_run): argument
52 for p in project.glob("**/*"):
81 twister_to_list(args.project, args.dry_run)
|
| D | migrate_includes.py | 28 def update_includes(project, dry_run): argument
29 for p in project.glob("**/*"):
84 update_includes(args.project, args.dry_run)
|
| D | migrate_sys_init.py | 22 def update_sys_init(project, dry_run): argument
23 for p in project.glob("**/*"):
90 update_sys_init(args.project, args.dry_run)
|
| /Zephyr-latest/doc/develop/tools/ |
| D | stm32cubeide.rst | 11 A project must have already been created with Zephyr and west.
28 #. Open your already existing project by going to
33 :alt: Create new CMake project
41 Press :guilabel:`Finish` and your project should now be available.
44 #. Right-click on the newly created project in the workspace, and select
54 :alt: Properties dialog for project
57 out-of-tree project or not.
86 #. You may now build the project using the :guilabel:`Build` button on the toolbar.
87 The project can be run using the :guilabel:`Run` button, as well as debugged
93 When configuring your project you see an error that looks similar to:
|
| /Zephyr-latest/doc/_doxygen/ |
| D | mainpage.md | 9 information about the project and becoming a member, and this [summary
11 to help you find your way around the project.
23 in the [project's GitHub LICENSE
25 There are some imported or reused components of the Zephyr project that
|
| /Zephyr-latest/tests/lib/sprintf/ |
| D | README.txt | 11 This project outputs to the console. It can be built and executed
20 Problems caused by out-dated project information can be addressed by
21 issuing one of the following commands then rebuilding the project:
|
| /Zephyr-latest/tests/kernel/mutex/sys_mutex/ |
| D | README.txt | 11 This project outputs to the console. It can be built and executed
20 Problems caused by out-dated project information can be addressed by
21 issuing one of the following commands then rebuilding the project:
|
| /Zephyr-latest/scripts/ |
| D | zephyr_module.py | 610 for project in projects[1:]:
611 meta_project, dirty = _create_meta_project(project.posixpath)
616 …if not meta_project.get("remote") or project.sha(MANIFEST_REV_BRANCH) != meta_project['revision'].…
618 if not meta_project.get('remote') or project.url != meta_project['remote']:
620 meta_project['url'] = project.url
628 if project.posixpath == manifest_path:
642 meta_module = _get_meta_project(meta_projects, module.project)
645 meta_module, dirty = _create_meta_project(module.project)
748 for project in modules + extra_modules:
750 if project == zephyr_base:
[all …]
|
| /Zephyr-latest/tests/crypto/tinycrypt_hmac_prng/ |
| D | README.txt | 10 This project outputs to the console. It can be built and executed
19 Problems caused by out-dated project information can be addressed by
20 issuing one of the following commands then rebuilding the project:
|
| /Zephyr-latest/tests/arch/arm/arm_sw_vector_relay/ |
| D | README.txt | 13 This project outputs to the console. It can be built and executed on QEMU as
22 Problems caused by out-dated project information can be addressed by
23 issuing one of the following commands then rebuilding the project:
|
| /Zephyr-latest/tests/ztest/zexpect/ |
| D | CMakeLists.txt | 6 project(base)
11 project(base)
|
| /Zephyr-latest/doc/security/ |
| D | vulnerabilities.rst | 22 - `Zephyr project bug tracker ZEPSEC-12
40 - `Zephyr project bug tracker ZEPSEC-17
59 - `Zephyr project bug tracker ZEPSEC-18
77 - `Zephyr project bug tracker ZEPSEC-20
97 - `Zephyr project bug tracker ZEPSEC-25
121 - `Zephyr project bug tracker ZEPSEC-26
148 - `Zephyr project bug tracker ZEPSEC-28
176 - `Zephyr project bug tracker ZEPSEC-29
204 - `Zephyr project bug tracker ZEPSEC-30
230 - `Zephyr project bug tracker ZEPSEC-35
[all …]
|
| /Zephyr-latest/cmake/ide/ |
| D | eclipse_cdt4_generator_amendment.cmake | 20 # errors, when the project was created with CMake generator and
58 # 5 - work mode: "C and CXX includes, defines in Eclipse with project defines"
65 ## 4 - work mode: "C and CXX includes, defines in .settings with project defines - [EXPERIMENTAL]"
71 message(" with project includes and defines")
75 message(" with project includes and defines")
79 # message(" without project defines")
81 # set(_work_mode "C and CXX includes, defines in .settings with project defines - [EXPERIMENTAL]")
84 set(_work_mode "C and CXX includes, defines in Eclipse with project defines")
102 if (${_work_mode} STREQUAL "C and CXX includes, defines in Eclipse with project defines")
116 …(${_work_mode} STREQUAL "C and CXX includes, defines in .settings with project defines - [EXPERIME…
[all …]
|
| /Zephyr-latest/tests/kernel/mem_protect/stackprot/ |
| D | README.txt | 11 This project outputs to the console. It can be built and executed
20 Problems caused by out-dated project information can be addressed by
21 issuing one of the following commands then rebuilding the project:
|
| /Zephyr-latest/tests/kernel/sleep/ |
| D | README.txt | 12 This project outputs to the console. It can be built and executed
21 Problems caused by out-dated project information can be addressed by
22 issuing one of the following commands then rebuilding the project:
|
