aboutsummaryrefslogtreecommitdiff
path: root/reproduce/analysis/make/download.mk
diff options
context:
space:
mode:
authorMohammad Akhlaghi <mohammad@akhlaghi.org>2019-08-01 12:48:15 +0100
committerMohammad Akhlaghi <mohammad@akhlaghi.org>2019-08-01 12:54:46 +0100
commit025dee1276a39e447042cc52fd91ed001d9047d6 (patch)
tree75585e7ab44e8abd634e9d53c87059c9684f768c /reproduce/analysis/make/download.mk
parent704fffcfb11d1b41e276bbb52624c393ff7e4428 (diff)
Bash startup script for every recipe
Until now the only way to define the environment of the Make recipes was through the exported Make variables (mostly in `initialize.mk' for the analysis steps for example). However, there is only so much you can do with environment variables! In some situations you want slightly more complicated environment control, like setting an alias or running of scripts (things that are commonly done in the `~/.bashrc' file of users to configure their interactive, non-login shells). With this commit, a `reproduce/software/bash/bashrc.sh' has been defined for this job (which is currently empty!). Every major Make step of the project adds this file as the `BASH_ENV' environment variable, so the shell that is created to execute a recipe first executes this file, then the recipe. Each top-level Makefile also defines a `PROJECT_STATUS' environment variable that enables users to limit their envirnoment setup based on the condition it is being setup (in particular in the early phase of `basic.mk', where the user can't make any assumption about the programs and has to write a portable shell script).
Diffstat (limited to 'reproduce/analysis/make/download.mk')
0 files changed, 0 insertions, 0 deletions