OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/cmake/toolchain/xtools/target.cmake

36 lines
1.3 KiB
CMake
Raw Normal View History

license: cleanup: add SPDX Apache-2.0 license identifier Update the files which contain no license information with the 'Apache-2.0' SPDX license identifier. Many source files in the tree are missing licensing information, which makes it harder for compliance tools to determine the correct license. By default all files without license information are under the default license of Zephyr, which is Apache version 2. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2019-04-06 21:08:09 +08:00
# SPDX-License-Identifier: Apache-2.0
xtools: Select correct ARM architecture for xtools Just like the zephyr SDK code, the xtools toolchain needs to select aarch64-zephyr-elf instead of arm-zephyr-eabi for the target triple when building for 64-bit ARM processors. Signed-off-by: Keith Packard <keithp@keithp.com>
2020-09-19 06:53:28 +08:00
if(CONFIG_ARM64)
set(CROSS_COMPILE_TARGET_arm aarch64-zephyr-elf)
else()
set(CROSS_COMPILE_TARGET_arm arm-zephyr-eabi)
endif()
cmake: Split toolchain configuration into pre-and post-DT Split up the toolchain configuration into two phases, generic and target. The 'generic' phase configures the toolchain just enough to be able to preprocess DT files. The 'target' phase completes the configuration with target-specific configuration. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
2018-12-13 23:32:07 +08:00
set(CROSS_COMPILE_TARGET_nios2 nios2-zephyr-elf)
cmake: toolchain/xtools: update to align with latest sdk-ng The target.cmake for xtools needs to be updated for changes in sdk-ng repo. This is simply a copy from the target.cmake for 0.10 SDK. Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2019-10-08 16:09:11 +08:00
set(CROSS_COMPILE_TARGET_riscv riscv64-zephyr-elf)
cmake: Split toolchain configuration into pre-and post-DT Split up the toolchain configuration into two phases, generic and target. The 'generic' phase configures the toolchain just enough to be able to preprocess DT files. The 'target' phase completes the configuration with target-specific configuration. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
2018-12-13 23:32:07 +08:00
set(CROSS_COMPILE_TARGET_mips mipsel-zephyr-elf)
set(CROSS_COMPILE_TARGET_xtensa xtensa-zephyr-elf)
set(CROSS_COMPILE_TARGET_arc arc-zephyr-elf)
cmake: xtools: use SoC name in path to xtensa toolchain Xtensa requires building a new toolchain for a specific SoC. By default xtools built Xtensa toolchains all have prefix of xtensa-zephyr-elf. In order to distinguish different toolchains, they are now placed in their own directories under their SoC name. This allows us to have multiple Xtensa toolchains targeting multiple SoCs. The additional level in path name is introduced in SDK v0.11 and sdk-ng master. Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2019-10-08 02:34:29 +08:00
set(CROSS_COMPILE_TARGET_x86 x86_64-zephyr-elf)
cmake: Added SPARC support This commit defines the tool prefix and command line options for the Zephyr SPARC architectural port. Signed-off-by: Martin Åberg <martin.aberg@gaisler.com>
2020-10-17 02:55:04 +08:00
set(CROSS_COMPILE_TARGET_sparc sparc-zephyr-elf)
cmake: Split toolchain configuration into pre-and post-DT Split up the toolchain configuration into two phases, generic and target. The 'generic' phase configures the toolchain just enough to be able to preprocess DT files. The 'target' phase completes the configuration with target-specific configuration. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
2018-12-13 23:32:07 +08:00
set(CROSS_COMPILE_TARGET ${CROSS_COMPILE_TARGET_${ARCH}})
set(SYSROOT_TARGET ${CROSS_COMPILE_TARGET})
cmake: xtools: use SoC name in path to xtensa toolchain Xtensa requires building a new toolchain for a specific SoC. By default xtools built Xtensa toolchains all have prefix of xtensa-zephyr-elf. In order to distinguish different toolchains, they are now placed in their own directories under their SoC name. This allows us to have multiple Xtensa toolchains targeting multiple SoCs. The additional level in path name is introduced in SDK v0.11 and sdk-ng master. Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2019-10-08 02:34:29 +08:00
if("${ARCH}" STREQUAL "xtensa")
set(SYSROOT_DIR ${TOOLCHAIN_HOME}/xtensa/${SOC_NAME}/${SYSROOT_TARGET})
set(CROSS_COMPILE ${TOOLCHAIN_HOME}/xtensa/${SOC_NAME}/${CROSS_COMPILE_TARGET}/bin/${CROSS_COMPILE_TARGET}-)
else()
set(SYSROOT_DIR ${TOOLCHAIN_HOME}/${SYSROOT_TARGET}/${SYSROOT_TARGET})
set(CROSS_COMPILE ${TOOLCHAIN_HOME}/${CROSS_COMPILE_TARGET}/bin/${CROSS_COMPILE_TARGET}-)
endif()
cmake: need to specify m32/m64 for x86_64 toolchain Since x86_64-zephyr-elf is a multi-lib toolchain, m32/m64 need to be specified for the compiler to return the correct library path when queried (e.g. --print-libgcc-file-name). This affects the compile check done by CMake. Without these flags, the compiler returns incorrect toolchain path (e.g. requiring 64-bit libraries but returning 32-bit library path). This also affects compiler flag checks for "-lstdc++". Incorrect library path results in error when checking for "-lstdc++", and this flag will not be used for the build. This results in undefined references when compiling C++ code. This creates target_x86.cmake to add the necessary flags for CMake to use. The target_x86_64.cmake is also created to mirror the same change. Also removing the -m32 flags for host-gcc since we are not building x86 targets with the host-gcc compiler. Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2019-10-08 16:14:02 +08:00
if("${ARCH}" STREQUAL "x86")
if(CONFIG_X86_64)
list(APPEND TOOLCHAIN_C_FLAGS -m64)
list(APPEND TOOLCHAIN_LD_FLAGS -m64)
else()
list(APPEND TOOLCHAIN_C_FLAGS -m32)
list(APPEND TOOLCHAIN_LD_FLAGS -m32)
endif()
endif()