diff options
| author | Mohammadreza Khellat <mkhellat@gmail.com> | 2020-08-26 14:53:10 +0400 |
|---|---|---|
| committer | Mohammad Akhlaghi <mohammad@akhlaghi.org> | 2020-08-27 12:40:16 +0100 |
| commit | c6a4aaad62a90af9a72f9bc58650696419474239 (patch) | |
| tree | f10a7af56ed23be9f95e76a5fdfd24e0f41a7f32 /reproduce/analysis/make | |
| parent | 9a0d968cde844304acc6c48f107184b71ce304fc (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')
| -rw-r--r-- | reproduce/analysis/make/paper.mk | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/reproduce/analysis/make/paper.mk b/reproduce/analysis/make/paper.mk index e207337..906b4d9 100644 --- a/reproduce/analysis/make/paper.mk +++ b/reproduce/analysis/make/paper.mk @@ -47,8 +47,9 @@ $(mtexdir)/project.tex: $(mtexdir)/verify.tex @if [ -f .local/bin/pdflatex ] && [ x"$(pdf-build-final)" != x ]; then # Put a LaTeX input command for all the necessary macro files. + # 'hardware-parameters.tex' is created in 'configure.sh'. rm -f $(mtexdir)/project.tex - for t in $(subst paper,,$(makesrc)); do + for t in $(subst paper,,$(makesrc)) hardware-parameters; do echo "\input{tex/build/macros/$$t.tex}" >> $(mtexdir)/project.tex done else @@ -113,7 +114,7 @@ $(texbdir)/paper.bbl: tex/src/references.tex $(mtexdir)/dependencies-bib.tex \ # do not use PGFPlots, then you should remove the `-shell-escape' # option for better security. See # https://savannah.nongnu.org/task/?15694 for details. - pdflatex -shell-escape -halt-on-error $$p/paper.tex + pdflatex -shell-escape -halt-on-error "$$p"/paper.tex biber paper fi @@ -142,11 +143,11 @@ paper.pdf: $(mtexdir)/project.tex paper.tex $(texbdir)/paper.bbl cd $(texbdir) # See above for a warning and brief discussion on the the # pdflatex option `-shell-escape'. - pdflatex -shell-escape -halt-on-error $$p/paper.tex + pdflatex -shell-escape -halt-on-error "$$p"/paper.tex # Come back to the top project directory and copy the built PDF # file here. - cd $$p + cd "$$p" cp $(texbdir)/$@ $(final-paper) fi |