Many of the modern build tools move away from that. CMake, for instance, drops the ability to build arbitrary assemblages of files and focuses almost exclusively on giving you a nicely-constrained language for defining compilation targets and allowing you to support many different compilers.
Maven, Ivy, and it's ilk focus on declaring run-time dependencies and on some concept of a "build l lifecycle."
Having used all these systems, I find that there are things I need to do when running a build that I can easily do in Make, but which are encumbered significantly by other tools.
Make's syntax sucks, and it expects you to know a bunch of arcane stuff about how your project is built, but in exchange you get the ability to build literally anything.
$ make -pf /dev/null | wc -l
359
Those suffix rules are enough for many projects, and a great example to follow if you need something different.But since Make is in use in so so many projects having good tutorials and material available is valuably to anyone who ends up needing to contribute to such an (open source) project.
CMake, for example, is less arcane, and can also generate project files for visual studio.
I'd agree that make shouldn't really be the go-to choice for brand new projects. It's limitations can encircle new projects.
I like the look of redo or tup.
I use tup widely across my personal projects and I must say, it has dramatically simplified my dev life.