aboutsummaryrefslogtreecommitdiff
path: root/reproduce/software/shell/git-pre-commit
diff options
context:
space:
mode:
authorMohammad Akhlaghi <mohammad@akhlaghi.org>2020-02-29 21:26:54 +0000
committerMohammad Akhlaghi <mohammad@akhlaghi.org>2020-02-29 21:37:33 +0000
commit7d0c5ef77395a44a316bb822170543b533db239c (patch)
tree710a4407a8aa2364bf96434e1a2a3927f9f3122c /reproduce/software/shell/git-pre-commit
parent2f0417995da0c21c894a003af5804b3c732a34c3 (diff)
IMPORTANT: re-preparation can only be done with --prepare-redo
Until now, the preparation phase was always executed before the final build phase when running `./project make'. But when it becomes necessary, project preparation can be slow and will un-necessarily slow down the project while the project is growing (focus is on the analysis that is done after preparation). With this commit, preparation will be done automatically the first time that the project is run (`.build/software/preparation-done.mk' doesn't exist). However, after preperation is complete once, future runs of `./project make' won't do preparation any more (by calling `top-prepare.mk'). They will directly call `top-make.mk' for the analysis. To manually invoke preparation after the first attempt, the `./project make' script should be run with the new `--prepare-redo' option. Also, since the preparation phase is now automatically done before the analysis phase, the long notice that describes running `./project make' at the end of the preparation phase has been removed in `top-prepare.mk'. It now just prints a short line, saying the preparation has been complete. Finally, when the project has not been run with the proper group configuration, it ends with an `exit 1' so the main `./project' script doesn't proceed any further.
Diffstat (limited to 'reproduce/software/shell/git-pre-commit')
0 files changed, 0 insertions, 0 deletions