I have convinced teams to switch to
justafter rewriting their makefiles in a fraction of the time and size. There have been some make die hards but they gave in to the team once they saw the justfiles.Luckily we didn’t have to write C or C++. I think the reason why that has so many build systems is because of the lack of a package manager. That entire world needs a
cargoequivalent.We’ve been doing fine for decades, thanks though!
For C/C++ make is a right tool for her job, but cmake is an improvement.
I’m personally all in on nix these days for dev work
There are already plenty of package manager options in the C++ world. Having an “official” one arguably only helps improve the onboarding experience, but overall it’s a chokepoint for the entire ecosystem. There are rarely “one size fits all” solutions to a problem, and there certainly isn’t one for a problem as complex as software builds and packaging.
There are? Where are the package registries? Could you give examples?
Conan and vcpkg are the two big ones I’m familiar with, but some projects use CMake FetchContent (with github acting as the CDN/registry), and depending on your requirements you can also just use system package managers on Linux, maybe Homebrew or Nix/Guix, or more niche ones like Spack. I’ve seen projects packaged using self hosted Pacman registries, and that works surprisingly well.
I don’t care who the CIA sends, I’m not using CMake 🙏
Yeah maybe, but usually if I’m using Make it’s because my use case is “I want users to be able to build stuff without having to install any more build tools”. The curse of network effects. That’s the only reason I’d ever use Bash too. Otherwise I’d switch to Nushell in a second.
Alternatively, don’t fix what ain’t broken.
Make is fine unless you want to build on Windows. Then you kind of need something else. It is the very slow process creation infrastructure that kills Make as a tool on Windows.
Make is fine unless you want to build on Windows. Then you kind of need something else.
I agree, you kind of need something else instead of Windows if you want to build software.
It is the very slow process creation infrastructure that kills Make as a tool on Windows.
s/Make as a tool on //
There should be a universal build system that is declarative, handles interdependent build steps, skips building outputs that are still fresh, but that checks freshness in a way that’s more robust than tracking modification times, manages parallel execution intelligently, and that manages arbitrary external dependencies. Oh hey, it’s Nix!
Can that scale down to individual .cpp files though? My understanding was that it works more at the package level.
Yes, it scales down to single files, and that is a common use case
Make still bests the author’s examples in certain use cases. I use it all the time in those cases and it’s fast and simple. Use the right tool for the job.
Give me a Make that
- properly handles filenames with arbitrary names (Make today breaks if filenames contain whitespace)
- uses space-based indentation level (Make today depends on the invisible difference between U+0008 TAB versus other whitespace, and refuses to process any other indentation)
Give me that, and… well, I’d probably still stick to current-day Make, because those improvements would cause my Makefiles to be backward incompatible. Make is just reliably available on pretty much any arbitrary system, unlike any candidate replacement.




