[cig-commits] r21099 - short/3D/PyLith/pylith_installer/trunk

[brad at geodynamics.org]

Author: brad
Date: 2012-12-05 11:02:09 -0800 (Wed, 05 Dec 2012)
New Revision: 21099

Modified:
   short/3D/PyLith/pylith_installer/trunk/INSTALL
Log:
Added more instructions to INSTALL.

Modified: short/3D/PyLith/pylith_installer/trunk/INSTALL
===================================================================
--- short/3D/PyLith/pylith_installer/trunk/INSTALL	2012-12-05 15:03:29 UTC (rev 21098)
+++ short/3D/PyLith/pylith_installer/trunk/INSTALL	2012-12-05 19:02:09 UTC (rev 21099)
@@ -59,11 +59,16 @@
 run some tests to make sure specific dependencies (PETSc and
 spatialdata) as well as PyLith were installed properly.
 
-We *STRONGLY* recommend that you run the configure script in a
-different directory from the PyLith Installer source code. We
-recommend creating a build directory (for example, $HOME/build/pylith)
-where you build any software with a subdirectory for PyLith.
+IMPORTANT: We *STRONGLY* recommend that you run the configure script
+  in a different directory from the PyLith Installer source code. We
+  recommend creating a build directory (for example,
+  $HOME/build/pylith) where you build any software with a subdirectory
+  for PyLith.
 
+WARNING: If you need to reconfigure the installer, then you should
+  remove all of your build and install files *BEFORE* running
+  configure. For example, rm -r $HOME/build/pylith $HOME/pylith
+
 These instructions are written assuming that you have downloaded the
 installer source code to $HOME/Downloads and want to use the following
 directories:
@@ -132,6 +137,8 @@
 STEP 2 - Run configure
 ----------------------------------------------------------------------
 
+Read the previous section "RUNNING THE INSTALLER"!!
+
 On multi-core and multi-processor systems (not clusters but systems
 with more than one core and/or processor), the build process can be
 sped up by using multiple threads when running "make". Use the