IMPORTANT: analysis outputs written in BDIR/analysis

Until now, the build directory contained a 'software/' directory (that
hosted all the built software), a 'tex/' subdirectory for the final
building of the paper, and many other directories containing
intermediate/final data of the specific project. But this mixing of built
software and data is against our modularity and minimal complexity
principles: built software and built data are separate things and keeping
them separate will enable many optimizations.

With this commit, the build directory of the core Maneage branch will only
contain two sub-directories: 'software/' and 'analysis/'. The 'software/'
directory has the same contents as before and is not touched in this
commit. However, the 'analysis/' directory is new and everything created in
the './project make' phase of the project will be created inside of this
directory.

To facilitate easy access to these top-level built directories, two new
variables are defined at the top of 'initialize.mk': 'badir', which is
short for "built-analysis directory" and 'bsdir', which is short for
"built-software directory".

HOW TO IMPLEMENT THIS CHANGE IN YOUR PROJECT. It is easy: simply replace
all occurances of '$(BDIR)' in your project's subMakefiles (except the ones
below) to '$(badir)'. To confirm if everything is fine before building your
project from scratch after merging, you can run the following command to
see where 'BDIR' is used and confirm the only remaning cases.

  $ grep -r BDIR reproduce/analysis/*
  --> make/verify.mk: innobdir=$$(echo $$infile | sed -e's|$(BDIR)/||g'); \
  --> make/initialize.mk:badir=$(BDIR)/analysis
  --> make/initialize.mk:bsdir=$(BDIR)/software
  --> make/initialize.mk:	$$sys_rm -rf $(BDIR)
  --> make/top-prepare.mk:all: $(BDIR)/software/preparation-done.mk

'BDIR' should only be present in lines of the files above. If you see
'$(BDIR)' used anywhere else, simply change it to '$(badir)'. Ofcourse, if
your project assumes BDIR in other contexts, feel free to keep it, it will
not conflict. If anything un-expected happens, please post a comment on the
link below (you need to be registered on Savannah to post a comment):

https://savannah.nongnu.org/task/?15855

One consequence of this change is that the 'analysis/' subdirectory can be
optionally mounted on a separate partition. The need for this actually came
up for some new users of Maneage in a Docker image. Docker can fix
portability problems on systems that we haven't yet supported (even
Windows!), or had a chance to fix low-level issues on. However, Docker
doesn't have a GUI interface. So to see the built PDF or intermediate data,
it was necessary to copy the built data to the host system after every
change, which is annoying during working on a project. It would also need
two copies of the source: one in the host, one in the container. All these
frustrations can be fixed with this new feature.

To describe this scenario, README.md now has a new section titled "Only
software environment in the Docker image". It explains step-by-step how you
can make a Docker image to only host the built software environment. While
your project's source, software tarballs and 'BDIR/analysis' directories
are on your host operating system. It has been tested before this commit
and works very nicely.

1 files changed, 42 insertions, 31 deletions

diff --git a/reproduce/software/shell/configure.sh b/reproduce/software/shell/configure.sh
index 24e8409..812f3d3 100755
--- a/reproduce/software/shell/configure.sh
+++ b/reproduce/software/shell/configure.sh
@@ -44,8 +44,8 @@ need_gfortran=0
 
 
 
-# Internal directories
-# --------------------
+# Internal source directories
+# ---------------------------
 #
 # These are defined to help make this script more readable.
 topdir="$(pwd)"
@@ -679,14 +679,14 @@ EOF
         fi
 
         # Then, see if the Fortran compiler works
-        testsource=$compilertestdir/test.f
+        testsourcef=$compilertestdir/test.f
         echo; echo; echo "Checking host Fortran compiler...";
-        echo "      PRINT *, \"... Fortran Compiler works.\""  > $testsource
-        echo "      END"                                      >> $testsource
-        if gfortran $testsource -o$testprog && $testprog; then
-            rm $testsource $testprog
+        echo "      PRINT *, \"... Fortran Compiler works.\""  > $testsourcef
+        echo "      END"                                      >> $testsourcef
+        if gfortran $testsourcef -o$testprog && $testprog; then
+            rm $testsourcef $testprog
         else
-            rm $testsource
+            rm $testsourcef
             cat <<EOF
 
 ______________________________________________________
@@ -1165,8 +1165,8 @@ rm -f "$finaltarget"
 
 
 
-# Project's top-level directories
-# -------------------------------
+# Project's top-level built software directories
+# ----------------------------------------------
 #
 # These directories are possibly needed by many steps of process, so to
 # avoid too many directory dependencies throughout the software and
@@ -1200,15 +1200,41 @@ if ! [ -d "$ictdir" ]; then mkdir "$ictdir"; fi
 itidir="$verdir"/tex
 if ! [ -d "$itidir" ]; then mkdir "$itidir"; fi
 
+# Temporary software un-packing/build directory: if the host has the
+# standard `/dev/shm' mounting-point, we'll do it in shared memory (on the
+# RAM), to avoid harming/over-using the HDDs/SSDs. The RAM of most systems
+# today (>8GB) is large enough for the parallel building of the software.
+#
+# For the name of the directory under `/dev/shm' (for this project), we'll
+# use the names of the two parent directories to the current/running
+# directory, separated by a `-' instead of `/'. We'll then appended that
+# with the user's name (in case multiple users may be working on similar
+# project names). Maybe later, we can use something like `mktemp' to add
+# random characters to this name and make it unique to every run (even for
+# a single user).
+tmpblddir="$sdir"/build-tmp
+rm -rf "$tmpblddir"/* "$tmpblddir"  # If its a link, we need to empty its
+                                    # contents first, then itself.
+
+
+
+
+
+# Project's top-level built analysis directories
+# ----------------------------------------------
+
+# Top-level built analysis directories.
+badir="$bdir"/analysis
+if ! [ -d "$badir" ]; then mkdir "$badir"; fi
+
 # Top-level LaTeX.
-texdir="$bdir"/tex
+texdir="$badir"/tex
 if ! [ -d "$texdir" ]; then mkdir "$texdir"; fi
 
 # LaTeX macros.
 mtexdir="$texdir"/macros
 if ! [ -d "$mtexdir" ]; then mkdir "$mtexdir"; fi
 
-
 # TeX build directory. If built in a group scenario, the TeX build
 # directory must be separate for each member (so they can work on their
 # relevant parts of the paper without conflicting with each other).
@@ -1224,7 +1250,6 @@ if ! [ -d "$texbdir" ]; then mkdir "$texbdir"; fi
 tikzdir="$texbdir"/tikz
 if ! [ -d "$tikzdir" ]; then mkdir "$tikzdir"; fi
 
-
 # If 'tex/build' and 'tex/tikz' are symbolic links then 'rm -f' will delete
 # them and we can continue. However, when the project is being built from
 # the tarball, these two are not symbolic links but actual directories with
@@ -1239,7 +1264,6 @@ else
     mv tex/build tex/build-from-tarball
 fi
 
-
 # Set the symbolic links for easy access to the top project build
 # directories. Note that these are put in each user's source/cloned
 # directory, not in the build directory (which can be shared between many
@@ -1247,7 +1271,9 @@ fi
 #
 # Note: if we don't delete them first, it can happen that an extra link
 # will be created in each directory that points to its parent. So to be
-# safe, we are deleting all the links on each re-configure of the project.
+# safe, we are deleting all the links on each re-configure of the
+# project. Note that at this stage, we are using the host's 'ln', not our
+# own, so its best not to assume anything (like 'ln -sf').
 rm -f .build .local
 
 ln -s "$bdir" .build
@@ -1260,21 +1286,6 @@ rm -f .gnuastro
 # ------------------------------------------
 
 
-# Temporary software un-packing/build directory: if the host has the
-# standard `/dev/shm' mounting-point, we'll do it in shared memory (on the
-# RAM), to avoid harming/over-using the HDDs/SSDs. The RAM of most systems
-# today (>8GB) is large enough for the parallel building of the software.
-#
-# For the name of the directory under `/dev/shm' (for this project), we'll
-# use the names of the two parent directories to the current/running
-# directory, separated by a `-' instead of `/'. We'll then appended that
-# with the user's name (in case multiple users may be working on similar
-# project names). Maybe later, we can use something like `mktemp' to add
-# random characters to this name and make it unique to every run (even for
-# a single user).
-tmpblddir="$sdir"/build-tmp
-rm -rf "$tmpblddir"/* "$tmpblddir"  # If its a link, we need to empty its
-                                # contents first, then itself.
 
 # Set the top-level shared memory location.
 if [ -d /dev/shm ]; then     shmdir=/dev/shm
@@ -1300,7 +1311,7 @@ fi
 # symbolic link to it. Otherwise, just build the temporary build
 # directory under the project build directory.
 if [ x"$tbshmdir" = x ]; then mkdir "$tmpblddir";
-else                        ln -s "$tbshmdir" "$tmpblddir";
+else                          ln -s "$tbshmdir" "$tmpblddir";
 fi