Zephyr is a bare metal build where standard libs are disabled. This means that c and runtime libraries must manually be linked in. This has generally been handled by using CMake's link libraries handling but the issue with that is both de-duplication but also library link order. Standard libraries must be linked at last location to ensure symbols are always available, however this is not optimal with target_link_libraries() because this would ultimately require every library to know the c library to link with, which is not desired. Therefore, setup standard C and runtime library linking in linker CMake files for toolchains where this is required. This commit expands the principle introduced with toolchain abstraction, see PR#24851. This means that a toolchain implementation may specify standard C, runtime, C++, etc libraries, as well as their link order. Because a property approach is used, then Zephyr modules, such as the Picolibc module can adjust such properties. An optional `zephyr_linker_finalize()` macro is called at the end of Zephyr's CMakeList process and can be used by the toolchain implementation to define the final linker invocation. This aligns the linker handling flow to the principle introduced in PR#24851 and improves the flexibility and robustness of Zephyr build system. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
53 lines
2 KiB
CMake
53 lines
2 KiB
CMake
# Copyright (c) 2024 Nordic Semiconductor
|
|
#
|
|
# SPDX-License-Identifier: Apache-2.0
|
|
|
|
check_set_linker_property(TARGET linker PROPERTY base
|
|
${LINKERFLAGPREFIX},--gc-sections
|
|
${LINKERFLAGPREFIX},--build-id=none
|
|
)
|
|
|
|
check_set_linker_property(TARGET linker PROPERTY baremetal
|
|
-nostdlib
|
|
-static
|
|
${LINKERFLAGPREFIX},-X
|
|
${LINKERFLAGPREFIX},-N
|
|
)
|
|
|
|
check_set_linker_property(TARGET linker PROPERTY orphan_warning
|
|
${LINKERFLAGPREFIX},--orphan-handling=warn
|
|
)
|
|
|
|
check_set_linker_property(TARGET linker PROPERTY orphan_error
|
|
${LINKERFLAGPREFIX},--orphan-handling=error
|
|
)
|
|
|
|
check_set_linker_property(TARGET linker PROPERTY memusage "${LINKERFLAGPREFIX},--print-memory-usage")
|
|
|
|
# -no-pie is not supported until binutils 2.37.
|
|
# If -no-pie is passed to old binutils <= 2.36, it is parsed
|
|
# as separate arguments -n and -o, which results in output file
|
|
# called "-pie".
|
|
if("${GNULD_VERSION_STRING}" VERSION_GREATER_EQUAL 2.37)
|
|
set_property(TARGET linker PROPERTY no_position_independent "${LINKERFLAGPREFIX},-no-pie")
|
|
else()
|
|
set_property(TARGET linker PROPERTY no_position_independent)
|
|
endif()
|
|
|
|
set_property(TARGET linker PROPERTY partial_linking "-r")
|
|
|
|
set_property(TARGET linker PROPERTY lto_arguments -flto -fno-ipa-sra -ffunction-sections -fdata-sections)
|
|
|
|
check_set_linker_property(TARGET linker PROPERTY no_relax ${LINKERFLAGPREFIX},--no-relax)
|
|
|
|
check_set_linker_property(TARGET linker PROPERTY sort_alignment
|
|
${LINKERFLAGPREFIX},--sort-common=descending
|
|
${LINKERFLAGPREFIX},--sort-section=alignment
|
|
)
|
|
|
|
# Some linker flags might not be purely ld specific, but a combination of
|
|
# linker and compiler, such as:
|
|
# --coverage for clang
|
|
# --gcov for gcc
|
|
# So load those flags now.
|
|
include(${ZEPHYR_BASE}/cmake/linker/${LINKER}/${COMPILER}/linker_flags.cmake OPTIONAL)
|