the HSL have been explicitely installed and shall be used
by the library. <code>no</code> otherwise.
(See the
- <a href="../readme.html#external-libs" target="body">ReadMe</a>
+ <a href="../readme.html#hsl" target="body">ReadMe</a>
file for more information on installation of HSL subroutines.)
</p>
</dd>
<code>yes</code> indicates whether the interfaces to the PETSc
library shall be compiled. <code>no</code> otherwise.
(See the
- <a href="../readme.html#external-libs" target="body">ReadMe</a>
+ <a href="../readme.html#petsc" target="body">ReadMe</a>
file for more information on installation of PETSc.)
</p>
</dd>
<code>yes</code> indicates whether the METIS library has been
detected upon configuration, and whether we shall interface with
it. <code>no</code> otherwise. (See the
- <a href="../readme.html#external-libs" target="body">ReadMe</a>
+ <a href="../readme.html#metis" target="body">ReadMe</a>
file for more information on installation of METIS.)
</p>
</dd>
Path and name of the library that contains the HSL
subroutines explicitely installed.
(See the
- <a href="../readme.html#external-libs" target="body">ReadMe</a>
+ <a href="../readme.html#hsl" target="body">ReadMe</a>
file for more information on installation of HSL
subroutines.)
</p>
Paths and names of the component libraries of the PETSc package, if
found and used at configuration time.
(See the
- <a href="../readme.html#external-libs" target="body">ReadMe</a>
+ <a href="../readme.html#petsc" target="body">ReadMe</a>
file for more information on installation of PETSc.)
</p>
</dd>
Path and name of the METIS libraries, if
found and used at configuration time.
(See the
- <a href="../readme.html#external-libs" target="body">ReadMe</a>
+ <a href="../readme.html#metis" target="body">ReadMe</a>
file for more information on installation of METIS.)
</p>
</dd>
PETSc include files and the PETSc architecture dependent include
files.
(See the
- <a href="../readme.html#external-libs" target="body">ReadMe</a>
+ <a href="../readme.html#petsc" target="body">ReadMe</a>
file for more information on installation of PETSC.)
</p>
</dd>
<dd> <p>
If METIS is used, then this variable has the path to the METIS
include files. (See the
- <a href="../readme.html#external-libs" target="body">ReadMe</a>
+ <a href="../readme.html#metis" target="body">ReadMe</a>
file for more information on installation of METIS.)
</p>
</dd>
include UMFPACK in the deal.II distributions courtesy of its author,
<a href="http://www.cise.ufl.edu/~davis/">Timothy A. Davis</a>.
</dd>
-
+
+ <a name="petsc"></a>
<dt>Petsc</dt>
<dd>
<acronym>deal.II</acronym> can interface to the <a
</p>
</dd>
+ <a name="metis"></a>
<dt>Metis</dt>
<dd>
<p>
declarations should not be a problem.
</p>
</dd>
-
+
+ <a name="blas"></a>
<dt>BLAS, LAPACK</dt>
<dd>If <code>--with-blas=blasname</code> and/or
<code>--with-lapack=lapackname</code> is given, provide wrappers
the default locations of your system, and similarly for LAPACK.
</dd>
+ <a name="netcdf"></a>
<dt>NetCDF</dt>
<dd>Autodetected if the <tt>NETCDF_DIR</tt> environment variable
points to a valid installation of the <a
format (GridIn::read_netcdf).
</dd>
-
+ <a name="hsl"></a>
<dt>Harwell Subroutine Library (HSL)</dt>
<dd>
It is possible to use some subroutines from the
<a href="external-libs/hsl.html" target="body">this page</a>.
</dd>
-
+ <a name="functionparser"></a>
<dt>FunctionParser</dt>
<dd>
There is a wrapper for the