3477b26ff6
If a custom command has a SYMBOLIC output (that is never actually created) then do not mark the custom command build statement as 'restat'. Otherwise other custom commands that depend on the symbolic output may not always re-run because after running the first custom command Ninja 'restat' will detect that the output timestamp did not change and skip its dependents. This was observed with the ExternalProject BUILD_ALWAYS option where Ninja would not re-run the 'install' step each time 'build' re-runs. |
||
|---|---|---|
| .. | ||
| C-Exe-Manifest.cmake | ||
| C-Exe-Manifest.step1.cmake | ||
| C-Exe-Manifest.step2.cmake | ||
| C-Exe.cmake | ||
| C-Exe.step1.cmake | ||
| C-Exe.step2.cmake | ||
| CMakeLists.txt | ||
| Custom-Always.cmake | ||
| RunCMakeTest.cmake | ||
| check.cmake | ||
| main.c | ||