Comment by epistasis
19 hours ago
I've spent a fair amount of time over the past decades to make autotools work on my projects, and I've never felt like it was a good use of time.
It's likely that C will continue to be used by everyone for decades to come, but I know that I'll personally never start a new project in C again.
I'm still glad that there's some sort of push to make autotools suck less for legacy projects.
You can use make without configure. If needed, you can also write your own configure instead of using auto tools.
Creating a make file is about 10 lines and is the lowest friction for me to get programming of any environment. Familiarity is part of that.
It's a bit of a balance once you get bigger dependencies. A generic autoconf is annoying to write, but rarely an issue when packaging for a distro. Most issues I've had to fix in nixpkgs were for custom builds unfortunately.
But if you don't plan to distribute things widely (or have no deps).. Whatever, just do what works for you.
Write your own configure? For an internal project, where much is under domain control, sure. But for the 1000s of projects trying to multi-plarform and/or support flavours/versions - oh gosh.
It depends on how much platform specific stuff you are trying to use. Also in 2025 most packages are tailored for the operating system by packagers - not the original authors.
Autotools is going to check every config from the past 50 years.
2 replies →
To extend on sibling comments:
autoconf is in no way, shape or form an "official" build system associated with C. It is a GNU creation and certainly popular, but not to a "monopoly" degree, and it's share is declining. (plain make & meson & cmake being popular alternatives)
I've stopped using autotools for new projects. Just a Makefile, and the -j flag for concurrency.
cmake ftw
Or meson is a serious alternative to cmake (Even better than cmake imho)
CMake also does sequential configuration AFAIK. Is there any work to improve on that somewhere?
Meson and cmake in my experience are both MUCH faster though. It’s much less of an issue with these systems than with autotools.
1 reply →
You mean cargo build
... can cargo build things that aren't rust? If yes, that's really cool. If no, then it's not really in the same problem domain.
3 replies →
cmake uses configure, or configure-like too!
Same concept, but completely different implementation.