summaryrefslogtreecommitdiff
path: root/doc/UsersGuide
diff options
context:
space:
mode:
authorallen <allen@17b73243-c579-4c4c-a9d2-2d5706c11dac>1999-02-14 19:32:47 +0000
committerallen <allen@17b73243-c579-4c4c-a9d2-2d5706c11dac>1999-02-14 19:32:47 +0000
commitac3596f7b8ca91fd632720ce79ad2c13e1d04b13 (patch)
treee68a95e94da30091d086da081145b506f0eefc52 /doc/UsersGuide
parent791bd4054b7f177f5df425dc5766a230529b51ca (diff)
Changes for changing names build->config and Standard Toolkit -> Base Package
git-svn-id: http://svn.cactuscode.org/flesh/trunk@267 17b73243-c579-4c4c-a9d2-2d5706c11dac
Diffstat (limited to 'doc/UsersGuide')
-rw-r--r--doc/UsersGuide/RunningCactus.tex20
-rw-r--r--doc/UsersGuide/UsersGuide.tex7
2 files changed, 14 insertions, 13 deletions
diff --git a/doc/UsersGuide/RunningCactus.tex b/doc/UsersGuide/RunningCactus.tex
index 059aec2c..36af0143 100644
--- a/doc/UsersGuide/RunningCactus.tex
+++ b/doc/UsersGuide/RunningCactus.tex
@@ -328,14 +328,14 @@ following files substructure:
\end{itemize}
When Cactus is first compiled it creates a new directory {\tt
-./CCTK/build/}. Disk space may be a problem on supercomputers where
+./CCTK/configs/}. Disk space may be a problem on supercomputers where
home directories are small. A workaround is to first create a
-build directory on scratch space, say {\tt scratch/cactus\_build/} (where
+configs directory on scratch space, say {\tt scratch/cactus\_configs/} (where
{\tt scratch/} is your scratch directory), and soft link ({\tt ln -s
-scratch/cactus\_build cactus/build/}) it to the Cactus directory.
+scratch/cactus\_configs cactus/configs/}) it to the Cactus directory.
When the code has been compiled for some configuration CONF, the
-directory {\tt build/CONF/} contains the following:
+directory {\tt configs/CONF/} contains the following:
\begin{itemize}
@@ -451,7 +451,7 @@ The gmake-process has to be repeated several times.
\begin{enumerate}
\item{}The first gmake-process configures the CCTK system by picking the
standard compilers, etc and creates a directory tree in {\tt
- ./build/CONF} which will later contain the configuration specific
+ ./configs/CONF} which will later contain the configuration specific
files.
\item{} You will ask to issue {\tt gmake <CONF>} again and you will be
presented a list of all thorns the CCTK has found. You will be
@@ -462,7 +462,7 @@ files.
no} the make process will continue.
\end{enumerate}
-The make process will set up subdirectories in the {\tt ./build}
+The make process will set up subdirectories in the {\tt ./configs}
directory that contain the configuration specific files. The directory
structure is
\begin{verbatim}
@@ -472,7 +472,7 @@ structure is
\begin{itemize}
\item{} Instead of using the editor to specify the thorns you want to
have compiled, you can {\em edit} the {\em ActiveThorns List} outside
- the make process. It is located in {\tt build/CONF/ActiveThorns},
+ the make process. It is located in {\tt configs/CONF/ActiveThorns},
wher {\tt CONF} refers to the name of your configuration.
For a completely new configuration, this directory exists {\em
after} the first make phase.
@@ -506,7 +506,7 @@ is to do.
\item {\tt gmake <CONF>-clean} cleans a configuration (rm -r *.o)
-\item {\tt gmake <CONF>-delete} deletes a configuration ({\tt rm -r build/<CONF>})
+\item {\tt gmake <CONF>-delete} deletes a configuration ({\tt rm -r configs/<CONF>})
\item {\tt gmake help} lists all make options
@@ -516,7 +516,7 @@ is to do.
\item {\tt gmake TAGS} creates an Emacs style TAGS file. See section
\ref{sec:TAGS} for using TAGS within Cactus.
-\item {\tt gmake distclean} nukes your build directory.
+\item {\tt gmake distclean} nukes your configs directory.
\item {\tt gmake downsize} removes non essential files as documents
and testsuites to allow for minimal installation size.
@@ -531,7 +531,7 @@ is to do.
This shoudl go with the thorn writing.}
Cactus compiles in all thorns listed in {\tt
-build/CONF/ActiveThorns}. {\q If the thorn has not been checked
+configs/CONF/ActiveThorns}. {\q If the thorn has not been checked
out...It IGNORES ?} Cactus looks for source code in a thorn's {\tt src}
directory. It first looks for a file {\tt make.code.defn} which
should contain
diff --git a/doc/UsersGuide/UsersGuide.tex b/doc/UsersGuide/UsersGuide.tex
index 648274f7..a8485389 100644
--- a/doc/UsersGuide/UsersGuide.tex
+++ b/doc/UsersGuide/UsersGuide.tex
@@ -1,4 +1,4 @@
-\documentstyle{report}
+\documentclass{report}
\parskip = 2 pt
\oddsidemargin = 0 cm
@@ -10,6 +10,7 @@
\def\t{\tt \obeylines }
\begin{document}
+\pagefooter{left}{center}{right}
\date{\verb$Date$}
@@ -17,7 +18,7 @@
\small{\verb$Revision$}
}
-\maketitle
+%\maketitle
@@ -63,7 +64,7 @@
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-\part{The Standard Toolkit}
+\part{The Base Package}
a) thorn\_IO
b) thorn\_PUGH