Trillinos - Revision history

Admin: Redirected page to Trilinos

2011-05-28T16:45:32Z

Redirected page to Trilinos

← Older revision		Revision as of 16:45, 28 May 2011
Line 1:		Line 1:
	~~=Installation=~~		#REDIRECT [[Trilinos]]

	~~==Configuring==~~

	~~===Trilinos 9===~~

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

	~~<source lang="bash">~~
	~~#!/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 \~~
	~~</source>~~

	~~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:~~

	~~<source>~~
	~~#!/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~~
	~~</source>~~

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

	* Source code location: <code>${HOME}/pkg/trilinos-10.6.0/trilinos-10.6.0-Source</code>
	* Build location: <code>${HOME}/pkg/trilinos-10.6.0</code>

	The CMake command given above is put into a script named <code>run_cmake.sh</code>, 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.~~

Admin: Created page with "=Installation= ==Configuring== ===Trilinos 9=== Trilinos 9 uses GNU autotools. The configure line to build Trilinos is as follows: #!/bin/sh # # configur..."

2011-04-08T17:25:40Z

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..."

New page

=Installation=

==Configuring==

===Trilinos 9===

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

<source lang="bash">
#!/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 \
</source>

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:

<source>
#!/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
</source>

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

* Source code location: <code>${HOME}/pkg/trilinos-10.6.0/trilinos-10.6.0-Source</code>
* Build location: <code>${HOME}/pkg/trilinos-10.6.0</code>

The CMake command given above is put into a script named <code>run_cmake.sh</code>, 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.