linux/poky.git/meta/recipes-devtools/cmake, branch kirkstone

cmake: fix CVE-2025-9301

2025-10-24T13:47:19+00:00

Reference: https://nvd.nist.gov/vuln/detail/CVE-2025-9301 https://gitlab.kitware.com/cmake/cmake/-/issues/27135 Upstream-patch: https://gitlab.kitware.com/cmake/cmake/-/commit/37e27f71bc356d880c908040cd0cb68fa2c371b8 (From OE-Core rev: 0aacc4298f2cdaaf6d19a58e6e134b6a6ecc5097) Signed-off-by: Saravanan Signed-off-by: Steve Sakoman

cmake: Correctly handle cost data of tests with arbitrary chars in name

2025-06-25T15:11:58+00:00

ctest automatically optimizes the order of (parallel) test execution based on historic test case runtime via the COST property (see [0]), which can have a significant impact on overall test run times. Sadly this feature is broken in CMake < 4.0.0 for test cases that have spaces in their name (see [1]). This commit is a backport of f24178f3 (which itself backports the upstream fix). the patch was adapted slightly to apply cleanly to the older CMake version in kirkstone. As repeated test runs are expected to mainly take place inside the SDK, the patch is only applied to 'nativesdk' builds. [0]: https://cmake.org/cmake/help/latest/prop_test/COST.html [1]: https://gitlab.kitware.com/cmake/cmake/-/issues/26594 Reported-By: John Drouhard (From OE-Core rev: f6a160f7ea57af6dfeca003e6c05aa42419fb755) Signed-off-by: Moritz Haase Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie Signed-off-by: Steve Sakoman

cmake: Fix sporadic issues when determining compiler internals

2024-11-15T14:05:32+00:00

When `-pipe` is enabled, GCC passes data between its different executables using pipes instead of temporary files. This leads to issues when cmake attempts to infer compiler internals via the `-v` parameter as each executable will print to `stderr` in parallel. In turn this may lead to compilation issues down the line as for example the system include directories could not be determined properly which may then propagate to issues such as: recipe-sysroot/usr/include/c++/11.3.0/cstdlib:75:15: fatal error: stdlib.h: No such file or directory | 75 | #include_next | | ^~~~~~~~~~ | compilation terminated. | ninja: build stopped: subcommand failed. | WARNING: exit code 1 from a shell command. Fix this stripping `-pipe` from the command line used to determine compiler internals. (From OE-Core rev: 8e2233fd0509b9f20c19d5006dd7ef0c2260bdba) Signed-off-by: Philip Lorenz Signed-off-by: Steve Sakoman

cmake: Unset CMAKE_CXX_IMPLICIT_INCLUDE_DIRECTORIES

2024-02-28T13:32:09+00:00

As discussion in [YOCTO #14717] cmake contains a OEToolchainConfig.cmake file to configure the toolchain correctly in cross-compile build for recipes using cmake. The variable CMAKE_CXX_IMPLICIT_INCLUDE_DIRECTORIES value updates incorrectly during do_compile the code. Due to this getting sporadic error like below, fatal error: stdlib.h: No such file or directory | 75 | #include_next | | ^~~~~~~~~~ | compilation terminated. | ninja: build stopped: subcommand failed. | WARNING: exit code 1 from a shell command. As cmake already correctly initializes the variable from environment, So we have to unset it in the toolchain file to avoid overwriting the variable definition again. (From OE-Core rev: 2b0b47fd0cafdb9de5025efda4140e11ea447afa) Signed-off-by: aszh07 Signed-off-by: Zahir Hussain Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit 5aeada5793af53e8c93940952d4f314474dca4c2) Signed-off-by: Steve Sakoman

cmake: Fix CMAKE_SYSTEM_PROCESSOR setting for SDK

2023-07-21T16:27:34+00:00

When building using an SDK, cmake complains that the target architecture 'cortexa53-crypto' is unknown. The same build in bitbake uses the target architecture 'aarch64'. Set CMAKE_SYSTEM_PROCESSOR the same as for bitbake. (From OE-Core rev: d877d5f07772ec4a05332068ddc03cf387313036) Signed-off-by: Tom Hochstein Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit d32a6225eefce2073a1cd401034b5b4c68351bfe) Signed-off-by: Steve Sakoman

cmake-native: Fix host tool contamination (Bug: 14951)

2022-11-09T17:42:08+00:00

Trying to build cmake-native on a host system where curl was built with cmake (resulting in CURLConfig.cmake and friends, which do not use the same naming schemes expected by cmake-native's build process, being installed to a system wide cmake directory like /usr/lib64/cmake/CURL) results in undefined references to all libcurl symbols. The problem is that cmake-native sees and uses the system wide /usr/lib64/cmake/CURL/CURLConfig.cmake, which defines CURL::libcurl and CURL::curl as opposed to setting ${CURL_LIBRARIES} as expected by cmake-native. find_package(CURL) (cmake-native's CMakeLists.txt, line 478) succeeds, but incorrectly uses the system wide CURLConfig.cmake, resulting CMAKE_CURL_LIBRARIES to be set to an empty string (cmake-native's CMakeLists.txt, line 484), causing the cmake-native build to miss -lcurl. The simplest fix is to let cmake know the right value for CURL_LIBRARIES. Making it -lcurl should always work with libcurl-native in recipe-sysroot-native. (From OE-Core rev: 0896d76a167dc9a64d69717ba66f12e7e1c41a77) Signed-off-by: Bernhard Rosenkränzer Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

cmake: remove CMAKE_ASM_FLAGS variable in toolchain file

2022-08-23T14:22:52+00:00

As discussied in [YOCTO #14717] cmake contains a OEToolchainConfig.cmake file to configure the toolchain correctly in cross-compile build for recipes using cmake. The CMAKE_ASM_FLAGS are the configuration are meant for assembly, but the spelling is incorrect and the Flag is ASFLAGS for gcc and other compilers. So this variable might neever have worked and it is better for recipes to specify their own. (From OE-Core rev: aeec7cc3081a7b21dc0e38b404547463796bfa0e) Signed-off-by: Martin Beeger Signed-off-by: Luca Ceresoli (cherry picked from commit 72729ffbab53f95ee9dd1bc22913d9b864495930) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

cmake: add missing licenses

2022-04-14T08:47:00+00:00

in target and native variant a different set of vendored libraries is pulled from the cmake sources. Add those licenses and there texts (From OE-Core rev: fc6c1951dd7e53791a9d92610dfc2eefab4c2a4a) Signed-off-by: Konrad Weihmann Signed-off-by: Richard Purdie

cmake: support to create per-toolchain cmake file in SDK

2022-03-31T16:52:59+00:00

The patch creates ${MULTIMACH_TARGET_SYS}-toolchain.cmake file at ${SDK_INSTALL_DIR}/sysroots/${SDK_SYS}/usr/share/cmake/, which is per-toolchain CMake toolchain file containing arch-specific values and independent of OE environment variables. The file gets created after installing SDK toolchain installer ined by running "bitbake -c populate_sdk ". The changes are similar to meson-setup.py which is used to create arch-specific ${SDK_INSTALL_DIR}/sysroots/${SDK_SYS}/usr/share/meson/*-meson.cross [YOCTO #14644] Tested-by: Jan Dorniak (From OE-Core rev: 42e68397ec74b3cd8ae5df45355c8f6254b48cd8) Signed-off-by: Jagadeesh Krishnanjanappa Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

cmake: upgrade 3.22.2 -> 3.22.3

2022-03-07T22:44:55+00:00

refresh 0001-CMakeDetermineSystem-use-oe-environment-vars-to-load.patch Changelog: ========== * The :command:'while' command again ignores errors in condition evaluation as CMake 3.21 and below did. This bug was fixed in 3.22.0, but exposed errors in existing projects. The fix has been reverted to restore compatibility. The fix may be restored in a future version of CMake via a policy. (From OE-Core rev: 146ceceaf81639085a82fd94d30ea84150a75e3a) Signed-off-by: Wang Mingyu Signed-off-by: Richard Purdie