I know little about gradle and have only just started exploring it, so this is just a question out of curiosity.
It’s supposedly a language agnostic dependency manager and builder, yet it seems to have only found its niche in Java. C/C++ projects could definitely do with dependency resolution…
You must log in or # to comment.
Here are a couple of reasons:
- C and C++ projects often predate Gradle by decades they will not change their build system without a compelling reason.
- Gradle is written in Java and requires a Java Runtime.
- At least for C++, CMake has pretty much become the standard build tool.
- Dependency resolution on Linux was ‘solved’ by relying on the distribution. Today, there also exist package managers for C and C++ like vcpkg or conan and they also integrate with CMake.
Cmake tends to be the upgrade path for sure, gradle is… hideous, i have having to use it for android.
no please don’t. Whenever I try to install something old and I realise it’s written in java I just give up after days of trying or end up with like 4 java versions installed and different dependencies need different versions.
I see gradle written while doing so, thus I associate it with HELL.
