Add a new configuration flag PROFILE=yes, which enables profiling in a

build.  This flag is equivalent to OPTIMISE=yes and DEBUG=yes.
Additional compiler options {C,CXX,F77,F90}_PROFILE_FLAGS are also
introduced.

The configuration stage sets the F77 flags to the F90 flags if an F90
compiler is found.  This flag setting was done too early, namely
before the default values for the F90 flags were set.  This flag
setting has been moved to a later time.

The link command used undefined make variables $(OPTIMISE_C) etc.
These variables have been removed.  Instead $(CXX_OPTIMISE_FLAGS)
etc. are added to the link statement.  This makes the linker pick up
the correct flags e.g. for profiling.


git-svn-id: http://svn.cactuscode.org/flesh/trunk@4327 17b73243-c579-4c4c-a9d2-2d5706c11dac

1 files changed, 42 insertions, 0 deletions

diff --git a/doc/UsersGuide/RunningCactus.tex b/doc/UsersGuide/RunningCactus.tex
index c4798dd6..41d8b09d 100644
--- a/doc/UsersGuide/RunningCactus.tex
+++ b/doc/UsersGuide/RunningCactus.tex
@@ -495,6 +495,22 @@ Current options are \texttt{yes}, \texttt{no}, or \texttt{memory}. The option
 \texttt{yes} switches on all debugging features, whereas \texttt{memory} just
 employs memory tracing (\ref{sec:metr}).
 
+\item [\texttt{C\_DEBUG\_FLAGS}]
+Debug flags for the C compiler, their use depends on the type of
+debugging being used.
+
+\item [\texttt{CXX\_DEBUG\_FLAGS}]
+Debug flags for the C++ compiler, their use depends on the type of
+debugging being used.
+
+\item [\texttt{F90\_DEBUG\_FLAGS}]
+Debug flags for the Fortran 90 compiler, their use depends on the
+type of debuggin being used.
+
+\item [\texttt{F77\_DEBUG\_FLAGS}]
+Debug flags for the Fortran 77 compiler, their use depends on the
+type of debugging being used.
+
 \item [\texttt{OPTIMISE, OPTIMIZE}]
 * Specifies what type of optimisation should be used. The only options currently
 available are \texttt{yes} and \texttt{no}.  The default is to use optimisation.\\
@@ -517,6 +533,32 @@ type of optimisation being used.
 Optimisation flags for the Fortran 77 compiler, their use depends on the
 type of optimisation being used.
 
+\item [\texttt{PROFILE}]
+  * Specifies what type of profiling should be used.  The only options
+  currently available are \texttt{yes} and \texttt{no}.  The default
+  is to use no profiling.
+
+\item [\texttt{C\_PROFILE\_FLAGS}]
+  Profile flags for the C compiler, their use depends on the type of
+  profiling being used.
+
+\item [\texttt{CXX\_PROFILE\_FLAGS}]
+  Profile flags for the C++ compiler, their use depends on the type of
+  profiling being used.
+
+\item [\texttt{F90\_PROFILE\_FLAGS}]
+  Profile flags for the Fortran 90 compiler, their use depends on the
+  type of profilin being used.
+
+\item [\texttt{F77\_PROFILE\_FLAGS}]
+  Profile flags for the Fortran 77 compiler, their use depends on the
+  type of profiling being used.
+
+\item [\texttt{WARN}]
+  * Specifies what type of build warnings should be used.  The only
+  options currently available are \texttt{yes} and \texttt{no}.  The
+  default is to produce no warnings.
+
 \item [\texttt{C\_WARN\_FLAGS}]
 Warning flags for the C compiler, their use depends on the type of
 warnings used during compilation (\ref{sec:gmopfobuco}).