mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-09-09 05:52:55 +00:00
8ba5aff8c0
When we move DT infront of Kconfig we are going to need access to a C toolchain before Kconfig is evaluated. This means it will not be possible to specify the toolchain used through Kconfig. To deal with this we ... Drop support for specifying CROSS_COMPILE through Kconfig. Still available is the ability to specify CROSS_COMPILE through the environment or through a CMake variable. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
26 lines
862 B
CMake
26 lines
862 B
CMake
# CROSS_COMPILE is a KBuild mechanism for specifying an external
|
|
# toolchain with a single environment variable.
|
|
#
|
|
# It is a legacy mechanism that will in Zephyr translate to
|
|
# specififying ZEPHYR_TOOLCHAIN_VARIANT to 'cross-compile' with the location
|
|
# 'CROSS_COMPILE'.
|
|
#
|
|
# New users should set the env var 'ZEPHYR_TOOLCHAIN_VARIANT' to
|
|
# 'cross-compile' and the 'CROSS_COMPILE' env var to the toolchain
|
|
# prefix. This interface is consisent with the other non-"Zephyr SDK"
|
|
# toolchains.
|
|
#
|
|
# It can be set from either the environment or from a CMake variable
|
|
# of the same name.
|
|
#
|
|
# The env var has the lowest precedence.
|
|
|
|
if((NOT (DEFINED CROSS_COMPILE)) AND (DEFINED ENV{CROSS_COMPILE}))
|
|
set(CROSS_COMPILE $ENV{CROSS_COMPILE})
|
|
endif()
|
|
|
|
set( CROSS_COMPILE ${CROSS_COMPILE} CACHE PATH "")
|
|
assert(CROSS_COMPILE "CROSS_COMPILE is not set")
|
|
|
|
set(COMPILER gcc)
|