From: David Wells
- Currently, the deal.II CMake Buildsystem
+ Currently, the deal.II CMake build system
recognizes
gcc,
clang, as well as
@@ -35,7 +35,7 @@
sets up reasonable default compiler flags.
FEATURE_<FEATURE>_DEPENDS (a variable)
- a variable which contains an optional list of other features
- this feature depends on (and which have to be enbled for this feature
+ this feature depends on (and which have to be enabled for this feature
to work.)
Features must be given with short name, i.e. without DEAL_II_WITH_
@@ -559,7 +559,7 @@ DEAL_II_FORCE_BUNDLED_<FEATURE> (an option)
DEAL_II_USER_INCLUDE_DIRS
DEAL_II_BUNDLED_INCLUDE_DIRS
@@ -668,7 +668,7 @@ SET(_inst
# ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/deal_ii_objects_(debug/release)
# so that it is available in global scope.
#
-# Header files and instatiation files (${_header}, ${_inst}) are added
+# Header files and instantiation files (${_header}, ${_inst}) are added
# for cosmetic reasons, so that they show up in IDEs.
#
DEAL_II_ADD_LIBRARY(obj_dofs OBJECT ${_src} ${_header} ${_inst})
diff --git a/doc/developers/porting.html b/doc/developers/porting.html
index 658b5c7a90..f49b08a049 100644
--- a/doc/developers/porting.html
+++ b/doc/developers/porting.html
@@ -27,7 +27,7 @@
Unknown compiler
-DDEAL_II_SETUP_DEFAULT_COMPILER_FLAGS=OFF
and set all
necessary compiler flags by hand via
@@ -78,7 +78,7 @@ include/deal.II/base/config.h.in
information might help:
expand_instantions
+ cannot be used). Locate the expand_instantiations
executable and export its location in the PATH
environment variable.
BUILD
: compilation error occured
+ BUILD
: compilation error occurred
RUN
: the test executable could not be run / aborted
@@ -431,7 +431,7 @@ category/test.[compiler=<regex>=<yes|no>.]*[with_<feature>=<
Normally, a test will be set up so that it runs twice, once in debug and
once in release configuration.
If a specific test can only be run in debug or release configurations but
- not in both it is possible to restrict the setup by prepeding
+ not in both it is possible to restrict the setup by prepending
.debug
or .release
directly before
.output
, e.g.:
@@ -652,7 +652,7 @@ $ ctest -V -R "category/my_new_test" make sure that the output is what you had expected. (For complex tests, it may sometimes be impossible to say whether the output is correct, and in this case we sometimes just take it to make - sure that future invokations of the test yield the same results.) + sure that future invocations of the test yield the same results.)diff --git a/doc/developers/writing-documentation.html b/doc/developers/writing-documentation.html index 62c2a45c65..17e6235376 100644 --- a/doc/developers/writing-documentation.html +++ b/doc/developers/writing-documentation.html @@ -357,7 +357,7 @@ void foobar () particular C++ constructs). On the other hand, showing code snippets in the introduction risks duplicating code in two places, which will eventually get out of synch. Consequently, - this intrstrument should only be used sparingly. + this instrument should only be used sparingly.
@@ -372,7 +372,7 @@ void foobar () create doxygen input that contains the comments of the program as text, and the actual code of the programs as code snippets. You can see this when you look at the pages for each of the tutorials - where the code is indendet relative to the text. + where the code is indented relative to the text.diff --git a/doc/users/cmakelists.html b/doc/users/cmakelists.html index a03ac2187a..8f7e30a6d7 100644 --- a/doc/users/cmakelists.html +++ b/doc/users/cmakelists.html @@ -869,7 +869,7 @@ DEAL_II_WITH_ZLIB
Make.global_options
- Above CMake configuration file
deal.IIConfig.cmake
is also + The above CMake configuration filedeal.IIConfig.cmake
is also available as a Makefile includable file calledMake.global_options
. It resides undershare/deal.II/Make.global_options
in the build and install