From: Wolfgang Bangerth
+
This document contains the following sections:
- A fairly complete C++ compiler. Various working compilers
+ A fairly complete C++ compiler. Various working compilers
are listed above. We do not support gcc versions older than
3.2 any more at this time.
Note that we are interested in writing portable C++, so if you find
@@ -118,7 +118,7 @@
Perl: Any Perl 5.x version should work.
+
Make: We use GNU make, version 3.78 or later which also
has rather good support for parallel builds, so you may
@@ -169,10 +169,10 @@
The library generates output in formats readable by
- GNUPLOT,
+ GNUPLOT,
GMV
- (general mesh viewer),
- Tecplot (ASCII and binary),
+ (general mesh viewer),
+ Tecplot (ASCII and binary),
Visualization Toolkit (Vtk),
AVS Explorer,
@@ -219,14 +219,14 @@
The whole library usually comes as a .tar.gz file, that is a
tarred file archive which is compressed with gzip. After unpacking
it with gunzip and tar (or tar xzf if you use GNU tar), you will
- find several subdirectories. First run the script
+ find several subdirectories. First run the script
Installation instructions and further information
+
Installation instructions and further information
on deal.II
-
@@ -36,7 +36,7 @@
-
+
System requirements
@@ -51,7 +51,7 @@
in the top-level directory,
which sets some paths and finds out what compiler you
use. ./configure supports several flags which are discussed
- further down below.
+ further down below.
./configure
@@ -252,7 +252,7 @@
After configuring, type `make', to obtain the following help (this - output may change slightly over time, just try it): + output may change slightly over time, just try it):
========================================================================
@@ -298,7 +298,7 @@
code of the classes in the /base
directory. These
are mostly helper classes (such as output of various data in
different data formats), and classes of general numerical
- interest (functions, tensors, etc.).
+ interest (functions, tensors, etc.).
lib/liblac
: lac
is the
@@ -323,7 +323,7 @@
- For each library, there will also be another one with an
+ For each library, there will also be another one with an
infix .g
between library name and suffix. The
difference between the two sets of libraries is the following:
@@ -357,7 +357,7 @@
-
The libraries without the .g
infix do not contain
- neither debugging information nor assertions. They are therefore much
+ neither debugging information nor assertions. They are therefore much
smaller and your program will run significantly faster (the
performance penalty of the .g
libraries is
between a factor of two and ten, depending on which parts of
@@ -370,7 +370,7 @@
they run stable and are used in production mode.
-
+
@@ -378,12 +378,12 @@
documentation files, by typing `make online-doc'; this takes some
minutes but you will
have (almost) all the documentation locally on your computer. You
- can access all documentation through this page.
- At this point, you have generated everything necessary to write
+ At this point, you have generated everything necessary to write
programs based on deal.II. If you are new to
deal.II, you may want to continue with the
tutorial.
@@ -471,13 +471,12 @@
- Currently supported CPUs are PowerPC64
, i386
,
- i486
, i586
, i686
,
- pentium
, pentium-mmx
, pentiumpro
,
- pentium2
, pentium3
, pentium4
,
- k6
, k6-2
, k6-3
, athlon
,
- athlon-tbird
, athlon-4
, athlon-xp
,
- athlon-mp
, opteron
, winchip-c6
, and winchip2
.
+ For a complete list of supported values of this switch, you may
+ take a look at the file aclocal.m4
in the top-level
+ directory. However, the most commonly used value
+ is --with-cpu=native
indicating that the compiler
+ should determine the CPU we are running on by itself and
+ optimize for it.
@@ -543,11 +542,11 @@
want a different version of UMFPACK, provide the path to that
version as an argument. Enabling UMFPACK adds the
class SparseDirectUMFPACK to the library. The default is to not
- use UMFPACK.
+ use UMFPACK.
If you want to use an external installation of UMFPACK, but UMFPACK was
- installed as
+ installed as
part of /usr
or /opt
, instead of local
directories in a home directory for example, you can use configure
switches --with-umfpack-include, --with-umfpack-libs
.
@@ -558,10 +557,10 @@
you want to use it with deal.II, please read it and make sure that you
agree with it. You can find the license of UMFPACK here. We
- include UMFPACK in the deal.II distributions courtesy of its author,
+ include UMFPACK in the deal.II distributions courtesy of its author,
Timothy A. Davis.
-
+
Petsc
@@ -571,7 +570,7 @@
library. The simplest way to do so is to set the PETSC_DIR
and PETSC_ARCH
environment variables. More information and
configuration options can be found here.
+ target="body">here.
@@ -586,7 +585,7 @@
pass --with-trilinos=/path/to/trilinos
to deal.II's ./configure
script. More
configuration options can be found here.
+ target="body">here.
@@ -618,7 +617,7 @@
switches --with-metis-include, --with-metis-libs
.
-
+
BLAS, LAPACK
@@ -646,22 +645,22 @@
libmyblas.a
or libmyblas.so
in the
directory /my/lib
and elsewhere in the system library
paths.
-
- Some versions of BLAS and LAPACK need additional libraries
- to be linked with. Such an example is the
+
+
Some versions of BLAS and LAPACK need additional libraries
+ to be linked with. Such an example is the
automatically tuned
linear algebra software (ATLAS). The BLAS version of this
- package also needs declarations from libatlas.a
,
+ package also needs declarations from libatlas.a
,
so it must be included. Using the standard library names of
atlas, the include for BLAS reads
./configure --with-blas='f77blas -latlas'
assuming that the library files libf77blas.a
and
- libatlas.a
or the respective shared libraries
- *.so
are in libraries included in
+ libatlas.a
or the respective shared libraries
+ *.so
are in libraries included in
LD_LIBRARY_PATH
. LAPACK generated by ATLAS is
- included in a similar fashion.
+ included in a similar fashion.
@@ -692,16 +691,16 @@
FunctionParser
- There is a wrapper for the
+ There is a wrapper for the
FunctionParser
- library, which has its own license; if you want to use it with deal.II,
- please read it and make sure that you agree with it.
- You can find the license of FunctionParser
+ library, which has its own license; if you want to use it with deal.II,
+ please read it and make sure that you agree with it.
+ You can find the license of FunctionParser
here. We
- include FunctionParser in the deal.II distributions courtesy of its author,
+ include FunctionParser in the deal.II distributions courtesy of its author,
Juha Nieminen.
-
-
+
+
@@ -719,14 +718,14 @@
feel free to ask if you have any problems with deal.II. If a
question is of general interest, you may want to use our mailing list,
which can be reached at
- dealii (at) dealii.org
+ dealii (at) dealii.org
and of which
previous mails are also archived online. Before writing to the
list, you will have to subscribe to it.
-
+
You can subscribe to this list by writing email to list-server
(at) dealii.org
with the text (not in the subject!)
@@ -736,7 +735,7 @@
The list server also understands the command help given
on a line by itself.
-
+
For specific problems, send email to either
Wolfgang.Bangerth, Ralf.Hartmann,
@@ -797,18 +796,18 @@
project homepage.
-
+
deal.II can interface with a number of other packages that you have to install
yourself. They are, of course, covered by their own licenses. In addition,
deal.II comes with a copy of UMFPACK and one of
+ href="http://www.cise.ufl.edu/research/sparse/umfpack/">UMFPACK and one of
FunctionParser,
- courtesy of their authors. UMFPACK and FunctionParser are covered by their
+ courtesy of their authors. UMFPACK and FunctionParser are covered by their
own licenses; please refer to their webpages to read them.
-
+
The deal.II mailing list
$Date$