I have no issue with projects like meson using FindFoo.cmake packages in principle. The problem with CMake is that most such packages aren’t implemented via jus

I have no issue with projects like meson using FindFoo.cmake packages in principle. The problem with CMake is that most such packages aren’t implemented via just an export, as in https://cmake.org/cmake/help/latest/guide/importing-exporting/index.html#exporting-targets https://cmake.org/cmake/help/latest/guide/importing-exportin... Such packages and exports are really just simple config files that I think can be safely treated as declarative — they become a perhaps uglier, but portable alternative to pkg-config. As such, having meson read them would be a smart move, and would be quite simple. Unfortunately, CMake doesn’t have a culture of creating/installing/using exports IME, and so you end up with enormous, complicated Find packages that do fancy bespoke dynamic search logic. THAT isn’t something I’d like a project like meson to lean on, but only because the goal should be to remove the need for such things, not depend on them further. CMake doesn’t help matters by making exports fiddly.