Searched refs:license (Results 1 – 25 of 42) sorted by relevance
12
| /Zephyr-latest/doc/develop/toolchains/ |
| D | arm_compiler.rst | 16 variable to point to your license file or server.
22 # Linux, macOS, license file:
24 # Linux, macOS, license server:
29 # Windows, license file:
31 # Windows, license server:
36 …<https://developer.arm.com/tools-and-software/software-development-tools/license-management/resour…
38 ``/opt/armds-2020-1`` with a Gold license, then set :envvar:`ARM_PRODUCT_DEF`
|
| D | iar_arm_toolchain.rst | 26 variable to be set to a valid ``license bearer token``.
|
| D | cadence_xcc.rst | 26 #. Make sure you have obtained a license to use the SDK, or has access to
|
| /Zephyr-latest/cmake/compiler/armclang/ |
| D | generic.cmake | 38 "And is the license setup correctly ?"
|
| /Zephyr-latest/cmake/toolchain/xt-clang/ |
| D | generic.cmake | 16 # obtain license information from remote licensing servers. So here
|
| /Zephyr-latest/cmake/toolchain/xcc/ |
| D | generic.cmake | 21 # obtain license information from remote licensing servers. So here
|
| /Zephyr-latest/soc/altr/zephyr_nios2f/cpu/ |
| D | ghrd_10m50da.qpf | 12 # applicable license agreement, including, without limitation,
|
| /Zephyr-latest/.github/ISSUE_TEMPLATE/ |
| D | 008_bin-blobs.md | 40 Document the license the blob(s) are distributed under
|
| D | 007_ext-source.md | 50 easy to use, and has a very liberal license.)
|
| /Zephyr-latest/boards/amd/acp_6_0_adsp/doc/ |
| D | index.rst | 55 First, make sure, the necessary license is available from
56 Cadence and set the license variables as per the instruction from Cadence.
|
| /Zephyr-latest/doc/_doxygen/ |
| D | mainpage.md | 22 Zephyr is permissively licensed using the Apache 2.0 license (as found
|
| /Zephyr-latest/doc/ |
| D | index.rst | 89 The Zephyr OS is provided under the `Apache 2.0 license`_ (as found in
119 .. _Apache 2.0 license:
|
| D | LICENSING.rst | 121 https://opensource.org/license/bsd-3-clause
|
| /Zephyr-latest/doc/develop/sca/ |
| D | polyspace.rst | 27 A license file must be available
28 in the installation folder. To request a trial license, visit `this
|
| D | cpptest.rst | 8 commercial license to use it.
|
| /Zephyr-latest/doc/contribute/ |
| D | external.rst | 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
32 other than the Apache 2.0 license needs to be fully understood in
186 the Apache-2.0 license, the submission process is complete and the external
189 If, however, the external source code uses a license other than Apache-2.0,
232 Tooling components must be released under a license approved by the
|
| D | bin_blobs.rst | 10 e.g. without corresponding source code released under an OSI approved license.
17 There are no limitations whatsoever (except perhaps license compatibility) in
24 Software license
29 license as part of the blob submission process. Blob vendors may impose a
139 distributed under a non-copyleft OSI approved license, that define the interface
156 released under an OSI approved license and documented using Doxygen.
|
| D | guidelines.rst | 51 .. _Apache 2.0 license:
56 Zephyr uses the `Apache 2.0 license`_ (as found in the LICENSE file in
59 to. The Apache 2.0 license is a permissive open source license that
69 https://www.whitesourcesoftware.com/whitesource-blog/top-10-apache-license-questions-answered/
71 A license tells you what rights you have as a developer, as provided by the
83 Importing code into the Zephyr OS from other projects that use a license
84 other than the Apache 2.0 license needs to be fully understood in
134 the right to submit the patch per the license. The DCO agreement is shown
144 have the right to submit it under the open source license
149 source license and I have the right under that license to
[all …]
|
| /Zephyr-latest/ |
| D | CONTRIBUTING.rst | 13 * Zephyr uses the permissive open source `Apache 2.0 license`_
|
| D | LICENSE | 69 copyright license to reproduce, prepare Derivative Works of,
76 (except as stated in this section) patent license to make, have made,
78 where such license applies only to those patent claims licensable
124 may provide additional or different license terms and conditions
135 the terms of any separate license agreement you may have executed
|
| /Zephyr-latest/doc/develop/ |
| D | modules.rst | 129 Zephyr CI, git lint, identity, and license checks directly on the set of
299 All source files in a module's codebase shall include a license header,
300 unless the module repository has **main license file** that covers source
301 files that do not include license headers.
303 Main license files shall be added in the module's codebase by Zephyr
305 and they contain a permissive OSI-compliant license. Main license files
306 should preferably contain the full license text instead of including an
307 SPDX license identifier. If multiple main license files are present it
308 shall be made clear which license applies to each source file in a module's
311 Individual license headers in module source files supersede the main license.
[all …]
|
| /Zephyr-latest/doc/develop/manifest/external/ |
| D | cannectivity.rst | 19 CANnectivity is licensed under the Apache-2.0 license.
|
| /Zephyr-latest/lib/posix/options/getopt/ |
| D | README | 58 [Project license: https://github.com/lattera/freebsd/blob/master/COPYRIGHT]
|
| /Zephyr-latest/doc/introduction/ |
| D | index.rst | 37 Zephyr is permissively licensed using the `Apache 2.0 license`_
43 .. _Apache 2.0 license:
|
| /Zephyr-latest/boards/gaisler/generic_leon3/doc/ |
| D | index.rst | 92 This software may only be used with a valid license.
|
12
