From charlesreid1

Revision as of 17:25, 8 April 2011 by Admin (talk | contribs) (Created page with "=Installation= ==Configuring== ===Trilinos 9=== Trilinos 9 uses GNU autotools. The configure line to build Trilinos is as follows: <source lang="bash"> #!/bin/sh # # configur...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Installation

Configuring

Trilinos 9

Trilinos 9 uses GNU autotools. The configure line to build Trilinos is as follows:

#!/bin/sh
#
# configure wrapper script
#
# ./runconfigure...
# make
# make install
#
# author:   charles reid
# date:     12-07-2008
#

./configure \
  CC=/sw/bin/gcc-4     \
  CXX=/sw/bin/g++-4    \
  F77=/sw/bin/gfortran \
  --prefix=$HOME/pkg/trilinos-9.0.1 \
  --disable-default-packages \
  --enable-aztecoo \
  --enable-epetra \
  --enable-epetraext \
  --enable-triutils \
  --enable-teuchos \
  --enable-amesos \
  --enable-amesos-lapack \
  --enable-amesos-klu \
  --enable-belos \
  --enable-didasko \
  MACOSX_DEPLOYMENT_TARGET=10.5 \

I have not tested this configure line on any targets other than Mac OS X 10.5.

Trilinos 10

For Trilinos version 10, the developers switched the make system to CMake. The CMake command I use to build Trilinos is:

#!/bin/sh
#
# ./run_cmake.sh
# make
# make install

cmake \
 -D CMAKE_BUILD_TYPE:STRING=DEBUG \
 -D Trilinos_ENABLE_ALL_PACKAGES:BOOL=ON \
 -D Trilinos_ENABLE_TESTS:BOOL=ON \
 CC=/sw/bin/gcc-4 \
 CXX=/sw/bin/g++-4 \
 F77=/sw/bin/gfortran \
 /path/to/trilinos-10.6.0-Source

The way I lay out the source and build directory are:

  • Source code location: ${HOME}/pkg/trilinos-10.6.0/trilinos-10.6.0-Source
  • Build location: ${HOME}/pkg/trilinos-10.6.0

The CMake command given above is put into a script named run_cmake.sh, which is in the build directory, and it is run. This generates the Makefile, and the next steps are "make" and "make install".

NOTE: Building all Trilinos packages takes a very long time (on an hours scale). To specify which packages to use, visit http://trilinos.sandia.gov and consult the documentation.