aboutsummaryrefslogtreecommitdiff
path: root/reproduce/analysis/make/prepare.mk
diff options
context:
space:
mode:
authorMohammadreza Khellat <mkhellat@gmail.com>2020-08-26 14:53:10 +0400
committerMohammad Akhlaghi <mohammad@akhlaghi.org>2020-08-27 12:40:16 +0100
commitc6a4aaad62a90af9a72f9bc58650696419474239 (patch)
treef10a7af56ed23be9f95e76a5fdfd24e0f41a7f32 /reproduce/analysis/make/prepare.mk
parent9a0d968cde844304acc6c48f107184b71ce304fc (diff)
Machine architecture and byte-order available as LaTeX macro
Until now, no machine-related specifications were being documented in the workflow. This information can become helpful when observing differences in the outcome of both software and analysis segments of the workflow by others (some software may behave differently based on host machine). With this commit, the host machine's 'hardware class' and 'byte-order' are collected and now available as LaTeX macros for the authors to use in the paper. Currently it is placed in the acknowledgments, right after mentioning the Maneage commit. Furthermore, the project and configuration scripts are now capable of dealing with input directory names that have SPACE (and other special characters) by putting them inside double-quotes. However, having spaces and metacharacters in the address of the build directory could cause build/install failure for some software source files which are beyond the control of Maneage. So we now check the user's given build directory string, and if the string has any '@', '#', '$', '%', '^', '&', '*', '(', ')', '+', ';', and ' ' (SPACE), it will ask the user to provide a different directory.
Diffstat (limited to 'reproduce/analysis/make/prepare.mk')
0 files changed, 0 insertions, 0 deletions