aboutsummaryrefslogtreecommitdiff
path: root/reproduce/config/pipeline/DIRECTORIES.mk.in
diff options
context:
space:
mode:
authorMohammad Akhlaghi <mohammad@akhlaghi.org>2018-02-14 14:13:36 +0100
committerMohammad Akhlaghi <mohammad@akhlaghi.org>2018-02-14 14:13:36 +0100
commitd26535d6665879f77d39e790b4aa9ee0dcb63dcf (patch)
treeabdd81f91d5fb5d11dc9e48ad39842c1cd988b62 /reproduce/config/pipeline/DIRECTORIES.mk.in
parent561dceda0fe880b155f8057eab78ee305ca66b80 (diff)
Sanity checks added, local settings now in LOCAL.mk.in
The choice of whether or not to make a PDF is now also a local system issue, not a general pipeline issue. So it has been put in the new `LOCAL.mk.in' file which replaces the old `DIRECTORIES.mk.in'. All local settings (things that when changed should not be version-controlled) should be defined in this file. A sanity check was added to find if `./configure' has been run before `make' or not (using the `LOCAL.mk' file which is an output of the configuration step). If `LOCAL.mk' doesn't exist, an error will be printed informing the user that `./configure' needs to be run first. The configure script also provides more clear and hopefully better information on its purpose and what must be done. Since `make clean', it is executed even when `./configure' hasn't been run, it will only delete the build directory and its contents when local configuration has been done. A `distclean' target was also added which will first "clean" the pipeline, then delete the `LOCAL.mk.in' file. To allow rules like `make' to be run even if `BDIR' isn't defined (`./configure' hasn't been run yet), a fake `BDIR' is defined in such cases.
Diffstat (limited to 'reproduce/config/pipeline/DIRECTORIES.mk.in')
-rw-r--r--reproduce/config/pipeline/DIRECTORIES.mk.in50
1 files changed, 0 insertions, 50 deletions
diff --git a/reproduce/config/pipeline/DIRECTORIES.mk.in b/reproduce/config/pipeline/DIRECTORIES.mk.in
deleted file mode 100644
index 9ebd67b..0000000
--- a/reproduce/config/pipeline/DIRECTORIES.mk.in
+++ /dev/null
@@ -1,50 +0,0 @@
-# Top-level user specific directories. Note the points below:
-#
-# - The VALUES to these directories are initially JUST PLACE-HOLDERS!
-# Please correct them based on your system.
-#
-# - The directories don't need to necessarily exist. If they do not exist,
-# they will be created and the necessary data will be downloaded into
-# them. Ofcourse provided that you have write permissions and an internet
-# connection.
-#
-# - Do not use the tilde expansion `~' or variables for your home
-# directory. Please use the full address, for example
-# `/home/your-user-name'.
-#
-# - An ending forward-slash `/' is NOT necessary. In the pipeline, all
-# these variables will be followed by a `/', so if you put a `/' at the
-# end of the value here, you will see a `//' in the printed outputs
-# during the processing. This has no technical problem, but can make
-# reading the outputs harder and is thus not recommended.
-
-
-
-
-
-# Input data directories
-# ----------------------
-#
-# This is where the input data (with the same file-name standard as the
-# online webpage) are stored. If this directory doesn't exist, or it
-# doesn't contain the files (with the correct file-name formats), it will
-# be created and the images will be downloaded. See
-# `reproduce/config/pipeline/web.mk', for the URLs containing the expected
-# inputs for each survey.
-SURVEY = reproduce/SURVEY
-
-
-
-
-
-# Build directory
-# ---------------
-#
-# This is where the intermediate outputs of each step are kept.
-#
-# Why a separate build directory? So the source and configuration files for
-# this reproduction pipeline do not get crowded by all the
-# intermediate/derivative files. Also to make synchronization and backups
-# more easy: the contents of the build directory do not need to be backed
-# up since they can be reproduced and they can be large.
-BDIR = reproduce/BDIR