Comment by kerkeslager
10 months ago
> If your goalpost is "change C to be like Rust and have a single build tool", then that's impossible. If your goalpost is "find me a tool that does X, Y, and Z", then there that is certainly possible. There are Cargo clones for C/C++ that work just fine.
My goal is to be able to build my project with as little effort as possible. "Effort" includes evaluating different tools and reading their documentation.
When selecting a language to write a new project in, the history of the language isn't something I care about.
If your goal is "I want to use Cargo and nothing else because that would require effort to learn to type a different command", then use Cargo.
But, there are similar build and package systems for C. Cargo is nothing special.
> If your goal is "I want to use Cargo and nothing else because that would require effort to learn to type a different command", then use Cargo.
That's not my goal, and you know that.
> But, there are similar build and package systems for C.
The reason you aren't naming one is that they obviously aren't similar in ways that matter.
> That's not my goal, and you know that.
Didn't you just say that you didn't want to read about any other build system, as that would involve effort? Uh... okay.
> The reason you aren't naming one is that they obviously _aren't_ similar in ways that matter.
Or, as I said previously, I'm not interested in endorsing build tools I haven't used, because I'm not in the market for a cargo clone. They exist. Plenty of folks I know are happy with one or another. Build tools are not difficult to write. As with the article, if you don't like existing build tools, spend an afternoon writing your own. It's a little graph theory and job management.
3 replies →