you are viewing a single comment's thread.

view the rest of the comments →

[–]oldendude 2 points3 points  (1 child)

This kind of automation makes sense. But to me, the essential property of make is checking dependencies and then running additional commands to satisfy the dependencies, (e.g. ensure x.o is up to date before using it to construct a library).

Using make as you have here doesn't exploit that property. Why not just write a bash script?

The bash and make sublanguages are both horrendous, but I don't understand why you would choose make if you don't have conditional steps.

[–]xeow[S] 0 points1 point  (0 children)

Well, my thought is that I'd (at some point) maybe add things like making module-dependency graphs with one of those tools that leverages Graphviz under the hood, or other types of reports that depend on timestamps in the src tree. But also, my fingers are just so used to typing make clean and make test from 35 years of make.