14927 2022-10-12 08:52:02 +0000 Meson >= 59.0 fails to find Threads dependency using CMake 2022-10-13 14:42:38 +0000 1 1 7 Build System, Metadata & Runtime OE-Core devtools / tool chain 4.0.2 x86 Multiple RESOLVED INVALID Undecided normal --- 1 toni.lammi unassigned meta.mr.watcher meta.watcher randy.macleod --- --- No (bug/feature does not impact docs) oldest_to_newest 94131 0 toni.lammi 2022-10-12 08:52:02 +0000 Meson fails when searching for Threads dependency using cmake: dependency('Threads', method: 'cmake', modules: ['Threads::Threads']) This issue was likely caused by an update to how Meson manages CMake dependencies: https://github.com/mesonbuild/meson/pull/8812 See also issue in meson: https://github.com/mesonbuild/meson/issues/10384 The issue only occurs with meson >= 59.0 I studied this issue a bit and found a couple workarounds for this in Yocto: First one is to modify cmake_toolchain_file in SDK's meson.cross from cmake_toolchain_file='<sdkpath>/usr/share/cmake/OEToolchainConfig.cmake' to cmake_toolchain_file='<sdkpath>/usr/share/cmake/cortexa53-crypto-<distro>-toolchain.cmake' Another one is to modify OEToolchainConfig.cmake from file( GLOB toolchain_config_files "${CMAKE_CURRENT_LIST_FILE}.d/*.cmake" ) to file( GLOB toolchain_config_files "${CMAKE_CURRENT_LIST_DIR}/*toolchain.cmake" ) To me it looks like the SDK's configuration is a bit off and meson therefore fails to get the correct information from the environment. I'm wondering if this behavior is a bug or if I'm doing something wrong here. 94135 1 toni.lammi 2022-10-12 11:53:55 +0000 Looking at this a bit more and I can see that the cmake_toolchain_file option comes from our own layer so I think this is not actually an oe-core issue. It seems that OE-core does not have support for this cmake-meson interoperability out-of-the-box. 94144 2 randy.macleod 2022-10-13 14:42:38 +0000 Seems to be specific to Toni's local layer.