Programming

18142 readers

82 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 2 years ago

MODERATORS

[email protected]

Why hasn't gradle been adopted for C/C++ projects? (programming.dev)

submitted 5 days ago by [email protected] to c/[email protected]

15 comments fedilink hide all child comments

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 are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 42 points 5 days ago (1 children)

Gradle is pretty awful actually, I’ve had to deal with it for years when I was writing Java. It’s pretty much the #1 reason I’ve stopped doing anything Java related.

Meson is the well designed option for C family languages. It also has support for Java, Rust, Swift, and a couple other languages. C is the most well supported though I think.

It also has a built-in dependency downloader that respects the system installed packages (and therefore distro packagers).

[–] Quetzalcutlass 12 points 5 days ago* (last edited 5 days ago) (1 children)

Gradle is so insanely over-engineered that it can do almost anything, yet so fragile that it can take weeks of bashing your head against the wall to get your build scripts working if you're doing anything remotely complicated with your setup (or even just upgrading Gradle versions). Everything is so finicky that even if you do things exactly as the documentation says, you'll still have to finagle things around nine times out of ten to get it to compile.

The user guide is longer than some novels.

[–] [email protected] -1 points 3 days ago* (last edited 3 days ago)

Gradle upgrades are dead simple… like yeah I get a bunch of the other criticisms of Gradle, but they mark things as deprecated two full major versions ahead and then slowly phase them out. Upgrades are a single command.

I haven’t really encountered the issues others are having and I’m guessing a lot of them occurred before Gradle’s switch to kotlin.

Edit: or the issues are actually from android build tool and not actually Gradle