2 ms·
> If you find yourself running "make clean" because it is "too dumb" you've built your Makefile wrong. What's built wrong is make itself. Because the signal it
by masklinn 5y ago
> If you find yourself running "make clean" because it is "too dumb" you've built your Makefile wrong.
What's built wrong is make itself. Because the signal it uses for "this dependency has changed" is the mtime, any change which does not move the mtime forwards will be ignored. Switching between concurrent git branches, for instance.
> Usually it means you've tried to manually re-create the inherent Make rules and have gotten it wrong somewhere.
And pray tell how do you "manually re-create the implicit make rules" when such rules don't exist? GNU Make has implicit rules for C, C++, Pascal, Fortran, Raftor, Modula-2, and assembly. That is, frankly, not much. And mostly outdated.