Timeline for C++ Mock Library: Part 2
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 25, 2023 at 16:42 | vote | accept | Loki Astari | ||
| Sep 18, 2023 at 6:18 | comment | added | G. Sliepen |
Ah, I see. So ideally you want to separate tracking whether the script ran from whether MockHeaderInclude.h was updated. This could be done by creating a dummy "stamp file" that is touched every time your script runs, and use that to compare against the timestamps of all the input files, instead of the timestamp of the script itself. That way you can still eliminate calls to your script if really nothing was changed.
|
|
| Sep 17, 2023 at 20:28 | comment | added | Loki Astari |
Just tried doing checking of timestamps. The problem here is that the output files depend on all the source (and header files). So any changes will force a rebuild of the MockHeaderInclude.h which will then force a rebuild of everything. Since we are always updating something before each build this results in rebuilding everything every time.
|
|
| Sep 16, 2023 at 21:15 | comment | added | G. Sliepen | That can in principle also be expressed in a make rule. | |
| Sep 16, 2023 at 20:59 | comment | added | Loki Astari |
Consider instead checking if any of the input files have a newer timestamp than the output file. Normally yes. But in this case they also have a dependency on the Build Tools themselves. If the build tools are updated I need to force a rebuild.
|
|
| Sep 16, 2023 at 10:15 | history | answered | G. Sliepen | CC BY-SA 4.0 |