classes/cmake: unset LDFLAGS in toolchain-native.bbclass

If a recipe is using toolchain-native.cmake to build native portion in a
non-native build, the target LDFLAGS from the environment will leak into
the native build.

This was noticed as building a SDK with clang means that LDFLAGS contains
a --dynamic-loader argument, so native binaries were trying to use the
target loader.

There are several variables that are set from LDFLAGS[1] so instead of
setting them all, we can simply unset the environment variable in the
toolchain.

[1] https://cmake.org/cmake/help/latest/envvar/LDFLAGS.html

(From OE-Core rev: f9fa240a6788188174c8080a78018ed9ce402f54)

Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Ross Burton
2025-09-26 15:33:39 +01:00
committed by Richard Purdie
parent fb086f85b7
commit 844539e848

View File

@@ -212,6 +212,15 @@ set( CMAKE_LIBRARY_PATH ${STAGING_BASE_LIBDIR_NATIVE} ${STAGING_LIBDIR_NATIVE})
list(APPEND CMAKE_C_IMPLICIT_INCLUDE_DIRECTORIES ${STAGING_INCDIR_NATIVE})
list(APPEND CMAKE_CXX_IMPLICIT_INCLUDE_DIRECTORIES ${STAGING_INCDIR_NATIVE})
# The assignmens above override CFLAGS and CXXFLAGS from the environment but
# not LDFLAGS, which ends up in CMAKE_EXE_LINKER_FLAGS. This then means our
# native builds use target flags, and can fail.
#
# As there are a number of variables that are set from LDFLAGS,
# clear it at source.
#
# https://cmake.org/cmake/help/latest/envvar/LDFLAGS.html
unset(ENV{LDFLAGS})
EOF
}