From: maier
- While developing the library itself it is often desirable
+ While developing the library itself, it is often desirable
to only compile certain parts. The build system generated by
- We expect that deal.II should work on the following
+ deal.II supports at least the following
platforms:
Most other combinations of POSIX-style operating systems and C++
- Standard compliant compilers should also work. If they don't, please
- report it as a bug.
+ Standard compliant compilers should also work. If they don't,
+ please report it as a bug.
@@ -48,7 +48,7 @@
-
cmake
again, either because one would like to change the configuration
parameters or because some configuration file (e.g., one of
- the CMakeLists.txt
files) have changed. (In fact,
+ the CMakeLists.txt
files) has changed. (In fact,
if the latter happens to be the case, then just
calling make
calls back and runs cmake
again automatically.) Either way, if that happens,
@@ -147,7 +147,7 @@
cmake
allows to build specific, selected targets.
A common scenario is that you only want to build debug or optimized
diff --git a/deal.II/doc/readme.html b/deal.II/doc/readme.html
index a9076f26b9..6ef16ecaec 100644
--- a/deal.II/doc/readme.html
+++ b/deal.II/doc/readme.html
@@ -58,19 +58,19 @@
deal.II is mostly developed on Linux using the
GCC compiler. However, it is not
platform specific and we strive to keep the source code C++
- standard compliant.
+ Standard compliant.
-
- There are many C++ compilers out there. Our experience is that, - unfortunately, most of them do not fully support the C++ 1998 standard - upon which we build, and they eventually fail on a project as large as - deal.II. Your best bet is to stick with the ones listed above. The only - platform where this is not trivial is Microsoft Windows where the widely - used Microsoft Visual C++ compiler simply has too many bugs supporting - advanced C++ code. + Please note that the Microsoft Visual C++ compiler, that is widely + used on Microsoft Windows, is not supported. If you need a native + Windows target, use the MinGW compiler instead.
@@ -99,8 +95,8 @@- In order to compile and use the deal.II - libraries you need to have the following programs installed: + In order to compile and use deal.II + you need to have the following programs installed:
@@ -180,7 +176,7 @@
- The whole library usually comes as a .tar.gz
file,
+ The whole library usually comes as a tar.gz
file,
which is a file archive compressed with gzip. After downloading it,
unpack it using either
@@ -217,7 +213,7 @@ make make install- These steps compile, link and install the deal.II libraries. The + These steps compile, link and install the deal.II library. The whole process should take between a few minutes and an hour, depending on your machine. @@ -235,7 +231,7 @@ number of simultaneous build processes you want
make
to use at any given time. Allowing make
to use
more simultaneous build processes (assuming you have that many
- processor cores) will greatly accelerate the build time.
+ processor cores) will greatly lower the build time.
tar
unpacked the file you downloaded) since
projects using deal.II should only need files that have been
installed. However, you will find it convenient to keep the source
- files around anyway, for two reasons: (i) When
+ files around anyway, for one reason: When
debugging you often end up with assertions for which you'd like to
- see the place in the library's source files that triggered it. (ii)
- You may want to use the tutorial programs located in the source
- directory.
+ see the place in the library's source files that triggered it.
CMake
system can accept a
significant number of configuration parameters. See the
@@ -313,8 +307,8 @@
All the documentation about the version that you downloaded and that can
- be found at the
- http://www.dealii.org/ domain can also be generated locally. To do
+ be found at the
+ http://www.dealii.org/ domain can also be generated locally. To do
so, invoke cmake
in the build instructions above as follows:
@@ -350,8 +344,9 @@deal.II has a large number of optional interfaces to - other libraries. By default,
cmake
will enable support - for all external libraries it can find in default paths. + other libraries. By default,cmake
will automatically + enable support for all external libraries it can find in default + paths. However, this behavior can be changed using command line switches to the initial call tocmake
. A detailed description can be found here. @@ -427,12 +422,12 @@ Notes:
-dev
or -devel
.
After that cmake
will automatically find the
- library and use it.
+ library and use it.
foo
can usually be done by specifying