Lines Matching full:code
6 In some cases it is desirable to leverage existing, external source code in
10 This section describes the circumstances under which external source code can be
20 code analysis, testing or simulation please refer to the
28 External source code licensed under the Apache-2.0 license is not subject to
31 Integrating code into the Zephyr Project from other projects that use a license
48 for contributed code, we ensure that the Zephyr community can develop products
54 Just like with any other regular contribution, one that contains external code
55 needs to be evaluated for merit. However, in the particular case of code that
59 Committee and evaluated carefully before the external source code is accepted
66 important for source code that deals with security or cryptography.
73 There are two ways of integrating external source code into the Zephyr Project,
80 The first way to integrate external source code into the project is to simply
81 import the source code files into the main ``zephyr`` repository. This
82 automatically implies that the imported source code becomes part of the
85 - The code is formatted according to the Zephyr :ref:`coding_style`
86 - The code adheres to the project's :ref:`coding_guidelines`
87 - The code is subject to the same checks and verification requirements as the
88 rest of the code in the main tree, including static analysis
99 The second way of integrating external source code into the project is to import
102 With this approach the code is considered as being developed externally, and
109 Integrating external code into the main :file:`west.yml` manifest file is
110 limited to code that is used by a Zephyr subsystem (libraries), by a platform,
130 There shall not be any direct dependency added in the Zephyr code tree (Git
131 repository) and all sample or test code shall be maintained as part of the module.
136 samples and test code in the Zephyr Git repository will be transitioned out
150 Regardless of the mode of integration, external source code that is integrated
152 integrate external source code must therefore commit to maintain the integration
153 of such code for the foreseeable future.
162 Before external source code can be included in the project, it must be reviewed
166 A request for external source code integration must be made by creating a new
168 about the source code and how it integrates into the project.
175 #. Use the :github:`New External Source Code Issue
179 Request that demonstrates the integration of the external source code and
185 source code is the best solution, and the external source code is licensed under
187 source code can be integrated.
189 If, however, the external source code uses a license other than Apache-2.0,
224 of the code compiled and linked into the final image. "Inclusion" in this