this post was submitted on 02 Apr 2026
170 points (99.4% liked)
Programming
26848 readers
524 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
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 !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Soo, how do i build Rust packages without Cargo?
You can run rustc directly! You just need to pass about 30 different parameters to it as well as a list of all the dependencies you use and...
Look, it works for small projects.
So i could theoretically script a wrapper?
I don't see why not. Cargo is fundamentally just a fancy wrapper around rustc, anyway. Sure, it's a really fancy wrapper that does a lot of stuff but it's entirely possible to just call rustc yourself.
The only reason to do this is if you're directly integrated Rust into an existing build system (e.g. Bazel). It's not going to help with this problem at all.
Why do you think cargo is a problem?
Not cargo per se, but even the tutorial for a cli-tool is like "setup clap, which has 20 dependencies and a kitchen sink". The whole (cargo-centric) ecosystem is much like Node, with the same problems.
And also, cargo.toml has inconsistencies and double-standards.
Can you expand on that?
That's cheating!
I will let you expand on this before responding to both: