To me, the most important feature of Ninja is that it can still track dependencies when a command produces multiple output files. In Make, if you have a step w

To me, the most important feature of Ninja is that it can still track dependencies when a command produces multiple output files. In Make, if you have a step with multiple outputs, it seems the usual thing to do is to lose track of all but one of them, and instruct the developer to run "make clean" when things stop working.