Configuration: .build and .local when bdir is given interactivelyHEADmaneage

Summary: will not affect existing configuration or analysis.

Until this commit, if the user gave the build directory interactively (had
not run './project configure' with '--build-dir'), the '.build' and
'.local' symbolic links were not created, resulting in a crash shortly
afterwards (when Maneage tried to write 'LOCAL.conf' in the build
directory!).

With this commit, the problem is solved by creating these links also when
the build directory is given interactively and after all the sanity checks
have passed.

1 files changed, 14 insertions, 0 deletions

diff --git a/reproduce/software/shell/configure.sh b/reproduce/software/shell/configure.sh
index 4887816..1771487 100755
--- a/reproduce/software/shell/configure.sh
+++ b/reproduce/software/shell/configure.sh
@@ -1146,6 +1146,20 @@ EOF
             echo " ** Please select another directory."
             echo ""
         else
+            # Set the '.build' and '.local' symbolic links (and delete
+            # possibly existing symbolic links). These commands are also
+            # present in the top-level 'project' script, but they are only
+            # invoked when '--build-dir' is called. When it is not called
+            # (the user wants to insert the directories interactively: the
+            # scenario here), the links need to be created from
+            # scratch. Furthermore, in case the given directory to
+            # '--build-dir' has problems (fails to pass the sanity checks
+            # above), the symbolic links also need to be recreated.
+            rm -f .build .local
+            ln -s $bdir .build
+            ln -s $bdir/software/installed .local
+
+            # Inform the user
             echo " -- Build directory set to ($instring): '$bdir'"
         fi
     done