Recipes inheriting meson.bbclass don't, by default, find dependencies using cmake. I created a simple repo to reproduce this issue: https://gitlab.com/toni.lammi.kone/meta-foo/-/tree/master/recipes-foo/app?ref_type=heads I've fixed this with a custom meson-cmake.bbclass with pretty trivial contents: ``` inherit cmake meson # This might be a meson bug, cmake executable is not found otherwise export CMAKE="cmake" do_write_config:append(){ # Point meson to correct cmake toolchain file to find dependencies correctly sed -i '/^\[properties\]/acmake_toolchain_file='"'${WORKDIR}/toolchain.cmake'" \ ${WORKDIR}/meson.cross } ``` I'm wondering if this should be handled in meson.bbclass directly? For instance MESON_USE_CMAKE variable which would enable this cmake functionality.
Inheriting both cmake and meson in the same recipe seems a little heavy-handed. I wonder how minimal a cmake toolchain file needs to be, considering it's only used for finding the module scripts?
Looked into this a bit more. All the cmake dependencies I've been having bad time with have a dependency to openssl which depends on threads. The build config fails when cmake's threads module tries to check if the compiler compiler supports -pthread flag. The build can be fixed by simply adding ``` set( CMAKE_CXX_COMPILER some-prefix-g++) ``` to the toolchain file. A similar setting is probably needed for C if the project uses that. Meson sets the same variable in its internal cmake toolchain but the value is an absolute path to the compiler. No idea who is at fault here: meson, cmake or FindOpenSSL.cmake.
You'd think an absolute path would be fine...
This enhancement is apparently not implemented so bump to 6.1.