Hot take after an afternoon un-fsck-ing a #CMake project: *Config.cmake files are so much harder to debug than *.pc#PKGConfig files, so not only are you trying to make sense of a Turing complete project definition but all the transitive dependencies that happen to use CMake too
@michelin On the flip side, meson's lack of extensibility and need to support everything from everyone itself means that it's a lot more language unstable than CMake. And I've seen some ugly hacking around Meson limitations in GNOME stuff... 😦
@Conan_Kudo for the 10% of the most complicated use cases maybe. But when something goes wrong with meson+pkgconfig the issue is obvious. With *Config.cmake... definitely not
It's Chef vs Ansible and Gradle vs Maven/Leiningen all over again
@Conan_Kudo@michelin Heh, I had a silly equivalent few weeks ago as well, if you run CMake into a symlinked directory it somehow gets an entirely wrong canonical path.
@lanodan@Conan_Kudo yeah... ideally a build system has an extension mechanism. But I still maintain that #KISS should be a guiding principle. Whether meson might be too inflexible, maybe
But yeah on the RISC V issue the RISC V people themselves are ... causing unnecessary trouble with their weird defaults
I used to be keen on that architecture but now am souring on it. On that @Conan_Kudo was right several years ago 🫠
Add comment