Searched full:toolchain (Results 1 – 25 of 1439) sorted by relevance
12345678910>>...58
| /Zephyr-latest/doc/develop/toolchains/ |
| D | custom_cmake.rst | 6 To use a custom toolchain defined in an external CMake file, :ref:`set these
9 - Set :envvar:`ZEPHYR_TOOLCHAIN_VARIANT` to your toolchain's name
11 toolchain's CMake configuration files.
13 Zephyr will then include the toolchain cmake files located in the
16 - :file:`cmake/toolchain/<toolchain name>/generic.cmake`: configures the
17 toolchain for "generic" use, which mostly means running the C preprocessor
20 - :file:`cmake/toolchain/<toolchain name>/target.cmake`: configures the
21 toolchain for "target" use, i.e. building Zephyr and your application's
24 Here <toolchain name> is the same as the name provided in
43 settings in a file named :file:`my-toolchain.cmake`, you can then invoke cmake
[all …]
|
| D | crosstool_ng.rst | 8 ``xtools`` toolchain variant is deprecated. The
9 :ref:`cross-compile toolchain variant <other_x_compilers>` should be used
10 when using a custom toolchain built with Crosstool-NG.
19 build your toolchain. Repeat as necessary to build toolchains for multiple
30 Currently, only i586 and Arm toolchain builds are verified.
35 - Set :envvar:`XTOOLS_TOOLCHAIN_PATH` to the toolchain build directory.
|
| D | designware_arc_mwdt.rst | 13 Even though ARC MWDT toolchain is used for Zephyr RTOS build, still the GNU preprocessor & GNU
16 … To setup ARC GNU toolchain please use SDK Bundle (Full or Minimal) instead of manual installation
17 of separate tarballs. It installs and registers toolchain and host tools in the system,
18 that allows you to avoid toolchain related issues while building Zephyr.
23 - Set :envvar:`ARCMWDT_TOOLCHAIN_PATH` to the toolchain installation directory. MWDT installation
28 If you have only one ARC MWDT toolchain version installed on your machine you may skip setting
|
| D | other_x_compilers.rst | 6 This toolchain variant is borrowed from the Linux kernel build system's
8 GNU-based cross toolchain.
15 toolchain set-up mechanism itself is supported.)
36 toolchain's binaries have, e.g. the path to the directory containing the
53 When using this option, all of your toolchain binaries must reside in the same
59 ``-``). If your toolchain is installed in ``/opt/mytoolchain/bin`` with binary
|
| /Zephyr-latest/include/zephyr/ |
| D | toolchain.h | 9 * @brief Macros to abstract toolchain specific capabilities
12 * utilize toolchain specific attributes and/or pragmas.
30 * on the toolchain-specific headers to define HAS_BUILTIN_x for the builtins
40 #include <toolchain/other.h>
42 #include <zephyr/toolchain/xcc.h>
44 #include <zephyr/toolchain/mwdt.h>
46 #include <zephyr/toolchain/armclang.h>
48 #include <zephyr/toolchain/llvm.h>
50 #include <zephyr/toolchain/gcc.h>
52 #error "Invalid/unknown toolchain configuration"
[all …]
|
| /Zephyr-latest/cmake/modules/ |
| D | FindHostTools.cmake | 74 # Default to the host system's toolchain if we are targeting a host based target
82 # Prevent CMake from testing the toolchain
88 # Support for out-of-tree toolchain
91 # Default toolchain cmake file
98 # but in case Zephyr's SDK toolchain is used, set TOOLCHAIN_HOME
103 set(TOOLCHAIN_ROOT ${TOOLCHAIN_ROOT} CACHE STRING "Zephyr toolchain root" FORCE)
104 assert(TOOLCHAIN_ROOT "Zephyr toolchain root path invalid: please set the TOOLCHAIN_ROOT-variable")
107 set(ZEPHYR_TOOLCHAIN_VARIANT ${ZEPHYR_TOOLCHAIN_VARIANT} CACHE STRING "Zephyr toolchain variant")
109 # Configure the toolchain based on what SDK/toolchain is in use.
110 include(${TOOLCHAIN_ROOT}/cmake/toolchain/${ZEPHYR_TOOLCHAIN_VARIANT}/generic.cmake)
[all …]
|
| D | FindZephyr-sdk.cmake | 12 # SDK and based on user / environment settings of selected toolchain decide if
23 # Zephyr toolchain variant to use if not defined already.
52 # Load Zephyr SDK Toolchain.
54 # 1) Zephyr specified as toolchain (ZEPHYR_SDK_INSTALL_DIR still used if defined)
55 # 2) No toolchain specified == Default to Zephyr toolchain
62 # No toolchain was specified, so inform user that we will be searching.
76 # The Zephyr SDK will automatically set the toolchain variant.
78 # then we keep track of current toolchain variant.
|
| /Zephyr-latest/boards/intel/adsp/ |
| D | twister.yaml | 3 toolchain:
16 toolchain:
40 toolchain:
46 toolchain:
53 toolchain:
|
| /Zephyr-latest/cmake/toolchain/cross-compile/ |
| D | Kconfig | 5 bool "Cross-compile toolchain supports TLS"
8 Set this if the cross-compile toolchain being used for the build
12 bool "Cross-compile toolchain supports GNU Extensions"
15 Set this if the cross-compile toolchain being used for the build
|
| D | generic.cmake | 4 # toolchain with a single environment variable.
11 # 'cross-compile' and the 'CROSS_COMPILE' env var to the toolchain
31 message(STATUS "Found toolchain: cross-compile (${CROSS_COMPILE})")
|
| /Zephyr-latest/boards/intel/adsp/doc/ |
| D | intel_adsp_ace15_mtpm.rst | 16 Xtensa Toolchain
19 If you choose to build with the Xtensa toolchain instead of the Zephyr SDK, set
21 Xtensa toolchain environment variables listed in :ref:`intel_adsp_generic`.
29 For older versions of the toolchain, set the toolchain variant to ``xcc``.
|
| /Zephyr-latest/cmake/toolchain/espressif/ |
| D | generic.cmake | 12 # find some toolchain
19 # Old toolchain installation path has been deprecated in 2.7.
22 # find some toolchain
52 "Unable to find toolchain in ${TOOLCHAIN_HOME} "
56 set(TOOLCHAIN_HAS_NEWLIB ON CACHE BOOL "True if toolchain supports newlib")
|
| /Zephyr-latest/cmake/toolchain/llvm/ |
| D | generic.cmake | 30 # Support for newlib is indicated by the presence of '_newlib_version.h' in the toolchain path.
34 set(TOOLCHAIN_HAS_NEWLIB ON CACHE BOOL "True if toolchain supports newlib")
37 # Support for picolibc is indicated by the presence of 'picolibc.h' in the toolchain path.
40 set(TOOLCHAIN_HAS_PICOLIBC ON CACHE BOOL "True if toolchain supports picolibc")
44 message(STATUS "Found toolchain: llvm (clang/ld)")
|
| /Zephyr-latest/cmake/toolchain/xtools/ |
| D | generic.cmake | 15 # a 'generic' toolchain until we know for sure which toolchain we
36 set(TOOLCHAIN_HAS_NEWLIB ON CACHE BOOL "True if toolchain supports newlib")
41 message(STATUS "Found toolchain: xtools (${XTOOLS_TOOLCHAIN_PATH})")
|
| /Zephyr-latest/include/zephyr/toolchain/ |
| D | armclang.h | 11 #error Please do not include toolchain-specific headers directly, use <zephyr/toolchain.h> instead
14 #include <zephyr/toolchain/llvm.h>
|
| /Zephyr-latest/include/zephyr/linker/ |
| D | linker-tool.h | 9 * @brief Toolchain-agnostic linker defs
12 * definitions (based on the toolchain) for the linker script.
26 #error "Unknown toolchain"
|
| /Zephyr-latest/scripts/coredump/gdbstubs/arch/ |
| D | xtensa.py | 32 # what toolchain Zephyr was built with; it assumed sample_controller
38 # SDK and Cadence's XCC toolchain. With the same SOC APL,
43 # only be built with Espressif's toolchain, but it's included for
52 def get_gdb_reg_definition(soc, toolchain): argument
58 if toolchain == XtensaToolchain.ZEPHYR:
60 elif toolchain == XtensaToolchain.XCC:
62 elif toolchain == XtensaToolchain.ESPRESSIF:
63 logger.error("Can't use espressif toolchain with CAVS. " +
159 # Get SOC and toolchain to get correct format for unpack
164 self.toolchain = XtensaToolchain(bytearray(arch_data_blk)[3])
[all …]
|
| /Zephyr-latest/doc/develop/languages/c/ |
| D | picolibc.rst | 44 :ref:`toolchain-bundled Picolibc in the Zephyr SDK
49 Toolchain Picolibc
56 The toolchain version of Picolibc can be enabled by de-selecting
60 For every release of Zephyr, the toolchain-bundled Picolibc and the
65 Building Without Toolchain bundled Picolibc
68 For toolchain where there is no bundled Picolibc, it is still
73 To build without toolchain bundled Picolibc, the toolchain must
75 this needs to be added to the toolchain Kconfig file:
85 when there is no toolchain bundled Picolibc.
|
| /Zephyr-latest/cmake/ |
| D | verify-toolchain.cmake | 2 # defined for proper toolchain use.
8 # cmake [options] -P verify-toolchain.cmake
16 message(FATAL_ERROR "verify-toolchain.cmake is a script and must be invoked "
17 "as:\n 'cmake ... -P verify-toolchain.cmake'\n"
|
| D | target_toolchain_flags.cmake | 1 # Uniquely identify the toolchain wrt. its capabilities.
7 # the MD5 will also change (as example toolchain upgrade in same folder)
35 # a new toolchain.
40 # Configure the toolchain flags based on what toolchain technology is used
|
| /Zephyr-latest/cmake/toolchain/xcc/ |
| D | generic.cmake | 3 include(${ZEPHYR_BASE}/cmake/toolchain/xcc/common.cmake)
12 -imacros${ZEPHYR_BASE}/include/zephyr/toolchain/xcc_missing_defs.h
25 message(STATUS "Found toolchain: xcc (${XTENSA_TOOLCHAIN_PATH})")
|
| /Zephyr-latest/cmake/toolchain/host/ |
| D | generic.cmake | 7 set(TOOLCHAIN_HAS_NEWLIB OFF CACHE BOOL "True if toolchain supports newlib")
9 message(STATUS "Found toolchain: host (gcc/ld)")
|
| /Zephyr-latest/boards/snps/nsim/arc_v/doc/ |
| D | index.rst | 45 The supported toolchains are listed in ``toolchain:`` array in ``.yaml`` file, where we can find:
47 * **zephyr** - implies RISC-V GNU toolchain from Zephyr SDK. You can find more information about
49 * **cross-compile** - implies RISC-V GNU cross toolchain, which is not a part of Zephyr SDK. Note t…
50 some (especially new) board targets may declare ``cross-compile`` toolchain support without
51 ``zephyr`` toolchain support because corresponding target CPU support hasn't been added to Zephyr
53 * **arcmwdt** - implies proprietary ARC MWDT toolchain. You can find more information about its
57 Note that even if both GNU and MWDT toolchain support is declared for the target some tests or
58 samples can be only built with either GNU or MWDT toolchain due to some features limited to a
59 particular toolchain.
139 * GNU & MWDT toolchain compiler options
[all …]
|
| /Zephyr-latest/scripts/pylib/twister/twisterlib/ |
| D | platform.py | 146 self.supported_toolchains = variant_data.get("toolchain", data.get("toolchain", []))
152 # toolchain ("zephyr", "cross-compile", "xtools" options) and for some targets we haven't
154 # targets can't be built with ARC MWDT toolchain ("arcmwdt" option) by Zephyr build system
155 # Instead for 'arc' we rely on 'toolchain' option in board yaml configuration.
164 # Xtensa is not listed on purpose, since there is no single toolchain
169 for toolchain in support_toolchain_variants[self.arch]:
170 if toolchain not in self.supported_toolchains:
171 self.supported_toolchains.append(toolchain)
|
| /Zephyr-latest/cmake/toolchain/arcmwdt/ |
| D | generic.cmake | 7 …message(STATUS "ARCMWDT_TOOLCHAIN_PATH is not set, use default toolchain from METAWARE_ROOT: '${ME…
13 …message(FATAL_ERROR "No MWDT toolchain specified: neither ARCMWDT_TOOLCHAIN_PATH nor METAWARE_ROOT…
31 # This workaround uses any (first awailable, independent on ARCH) toolchain from SDK for DTC prepro…
53 set(TOOLCHAIN_HAS_NEWLIB OFF CACHE BOOL "True if toolchain supports newlib")
|
12345678910>>...58
