From faa3bfacb762587a96ef45d07f70765fbca1254b Mon Sep 17 00:00:00 2001
From: maier cmake
, the cmake
program
creates a cache in the current (build) directory that contains
- the values of all cached variables that had previously been passed
+ the values of all (cached) variables that had previously been passed
as command line arguments, been found through running tests,
or had otherwise been set.
- Normally, one will then simply build the library in this
- directory by calling make
and install it. If the
- library changes, one would just call make
again and
- it would only re-compile those files that depend on those sources
- that have changed. In other words, one will rarely have to deal
- with the cached variables at all.
+ Normally, after running cmake
one will simply build
+ the library by calling make
. If the library changes,
+ a subsequent call to make
will only re-compile those
+ files that depend on sources that have changed. In other words,
+ one will rarely have to deal with the cached variables at all.
@@ -89,10 +88,9 @@
calling make
calls back and runs cmake
again automatically.) Either way, if that happens,
then cmake
will only run whatever tests are really
- necessary; values for variables that are already in the cache
- are not re-evaluated. This means that calling cmake
- a second time without any arguments at all in a situation like
- this
+ necessary; values for variables that are already in the cache
+ are not re-evaluated. This means that calling cmake
+ a second time without any arguments at all in a situation like this
mkdir build @@ -103,7 +101,7 @@ has absolutely no effect: In particular, the second time around it uses theswitches off support for the METIS library that may have been - automatically detected the first time around but that we really - didn't want to link with. + automatically detected during the first invocation of +CMAKE_INSTALL_PREFIX
value previously passed, along with all other arguments one may have had on the - first invokation. This is different from the way + first invocation. This is different from the way theautoconf/configure
mechanism worked. @@ -139,13 +137,14 @@ cmake -DDEAL_II_WITH_METIS=OFF ../
cmake
but that we really didn't want to link with.
Just like with simple make
, cmake
@@ -154,7 +153,8 @@
are. The most common scenario is that you only want to build
debug or optimized libraries. This can be achieved using the
following commands in the build directory:
- TODO: This is a bit misleading, as make install
won't succeed
+ TODO: This is a bit misleading, as make install
+ always implies make all
.
make deal_II.g # only debug library @@ -444,6 +444,25 @@Build configuration
++
CMAKE_BUILD_TYPE
controls the type of build. + We support theDebug
,Release
+ andDebugRelease
build targets. Default is the +DebugRelease
target. +
Debug
will compile a debug library
+ libdeal_II.g.so
+ Release
will build an optimized
+ libdeal_II.so
.
+ DebugRelease
will build both libraries
+
deal.II will configure sensible default CFLAGS
and
CXXFLAGS
depending on platform, compiler and build
--
2.39.5