wrote: CMake's default is to allow downloads. It's possible to write CMake projects so that they try find_package first and then fall back to downloading. I think FETCHCONTENT_FULLY_DISCONNECTED might

lists.openembedded.org wrote: The Java OSS ecosystem has had fairly well defined build time and runtime dependency metadata commonly available for many years now. The more widely used build tools are

https://cmake.org/cmake/help/v3.16/module/FindGTest.html#result-variables Thank you for providing more details. The gmock target can be backported to dunfell in an alternative way, by leaving out the

lists.openembedded.org wrote: I offer "denylist". Cheers, Eero

lists.openembedded.org wrote: Bump. The googletest recipe at meta-oe dunfell branch is for version 1.10. The fact that CMake Find Module masked the targets of the GTest package resulted in a number of

You can use `${pcfiledir}/../..` within a pkg-config file to reference the install path. Unfortunately the last time I tried it when cross-compiling, the PKG_CONFIG_SYSROOT_DIR was ended up in the pat

`googlemock` has been absorbed into the [googletest](https://github.com/google/googletest) project and is built and installed from the same source tree. `googletest` has provided a CMake Config-file P