Home
last modified time | relevance | path

Searched full:toolchains (Results 1 – 25 of 88) sorted by relevance

1234

/Zephyr-latest/scripts/west_commands/
Dsdk.py101 --interactive, --toolchains, --no-toolchains and --no-hosttools options
147 … "--toolchains, --no-toolchains and --no-hosttools will be ignored if this option is enabled.",
151 "--toolchains",
155 "If this option is not given, toolchains for all architectures will be installed.",
159 "--no-toolchains",
161 help="do not install toolchains. "
162 "--toolchains will be ignored if this option is enabled.",
372 if not args.toolchains:
375 for tc in args.toolchains:
425 # checking toolchains parameters
[all …]
/Zephyr-latest/doc/develop/toolchains/
Dindex.rst3 Toolchains chapter
6 Guides on how to set up toolchains for Zephyr development.
Dother_x_compilers.rst10 Examples of such "other cross compilers" are cross toolchains that your Linux
12 from the net. Unlike toolchains specifically listed in
13 :ref:`toolchains`, the Zephyr build system may not have been
17 Follow these steps to use one of these toolchains.
Dcrosstool_ng.rst12 You can build toolchains from source code using crosstool-NG.
19 build your toolchain. Repeat as necessary to build toolchains for multiple
Dhost.rst3 Host Toolchains
Dcustom_cmake.rst3 Custom CMake Toolchains
/Zephyr-latest/cmake/toolchain/xtools/
Dgeneric.cmake14 # Choose one of the toolchains in 'TOOLCHAIN_HOME' at random to use as
17 # toolchains because choosing between iamcu and non-iamcu is dependent
/Zephyr-latest/cmake/linker/
Dtarget_template.cmake7 # This file will define optional linker macros for toolchains that are not
/Zephyr-latest/doc/develop/
Dindex.rst22 toolchains/index
/Zephyr-latest/cmake/toolchain/cross-compile/
Dgeneric.cmake13 # toolchains.
/Zephyr-latest/.github/workflows/
Derrno.yml29 … echo "ZEPHYR_SDK_INSTALL_DIR=/opt/toolchains/zephyr-sdk-$( cat SDK_VERSION )" >> $GITHUB_ENV
Dhello_world_multiplatform.yaml62 toolchains: all
Dtwister_tests_blackbox.yml53 echo "ZEPHYR_SDK_INSTALL_DIR=/opt/toolchains/zephyr-sdk-$( cat SDK_VERSION )" >> $GITHUB_ENV
/Zephyr-latest/include/zephyr/toolchain/
Dcommon.h18 * Macros to abstract compiler capabilities (common to all toolchains).
84 /* .align assembler directive is supposed by all ARC toolchains and it is
85 * implemented in a same way across ARC toolchains.
/Zephyr-latest/boards/mediatek/
Dindex.rst93 Toolchains section in Mediatek Audio DSPs
101 toolchains in the SDK may not be. The overlay files for the device
155 toolchains. Support for those tools is beyond the scope of this
/Zephyr-latest/lib/libc/newlib/
DCMakeLists.txt9 # Zephyr normally uses -ffreestanding, which with current GNU toolchains
/Zephyr-latest/doc/develop/getting_started/
Dinstallation_mac.rst30 is however relevant for most :ref:`toolchains`.
Dinstallation_linux.rst210 The Zephyr Software Development Kit (SDK) contains toolchains for each of
300 toolchains for all Zephyr target architectures, and does not require any extra
304 toolchain as described in the :ref:`toolchains` section.
/Zephyr-latest/boards/snps/nsim/arc_v/doc/
Dindex.rst39 Most board targets support building with both GNU and ARC MWDT toolchains, however
41 toolchains for the board targets in the corresponding ``.yaml`` file.
45 The supported toolchains are listed in ``toolchain:`` array in ``.yaml`` file, where we can find:
/Zephyr-latest/cmake/
Dtarget_toolchain_flags.cmake18 # Toolchains with the same signature will always support the same set of flags.
/Zephyr-latest/doc/develop/languages/c/
Dminimal_libc.rst13 with a number of different toolchains.
/Zephyr-latest/cmake/compiler/xcc/
Dtarget.cmake6 # GCC-based toolchains
/Zephyr-latest/doc/develop/languages/cpp/
Dindex.rst139 limited number of toolchains. Zephyr does not.
146 files are exposed to a much larger variety of toolchains and project
201 toolchains and standards, designated initializers in Zephyr header files
/Zephyr-latest/samples/basic/blinky/
DREADME.rst54 On GCC-based toolchains, the error looks like this:
/Zephyr-latest/include/zephyr/linker/
Dlinker-tool-mwdt.h78 * own parameter since it needs abstraction across the different toolchains.

1234