[Trilinos-Users] sample makefiles

[Mike Heroux]

Gideon,
 
Trilinos provides a record of all compilers, parameters and dependencies
used to create a particular build.  This information is contained in a
collection of files Makefile.export.package_name and
Makefile.export.package_name.macros that, once you do "make install", will
be in the include directory.
 
You only need to include the Makefile.export.* information from the packages
that are higher level, since the high level Makefile.export.* files
recursively include the same files for package upon which they depend.  For
example, if you are using AztecOO and include its Makefile.export.* files,
the Makefile.export.* files of Epetra will also be included.
 
A simple example makefile that is easy to modify for most situations is at
the following link, about half-way down the page.  (The page is from last
year's ACT Toolkit hands-on session.)
 
http://www.cs.sandia.gov/~maherou/acts/acts.htm 
 
Mike


  _____  

From: trilinos-users-bounces at software.sandia.gov
[mailto:trilinos-users-bounces at software.sandia.gov] On Behalf Of Gideon
Simpson
Sent: Saturday, April 21, 2007 12:31 PM
To: trilinos-users at software.sandia.gov
Subject: [Trilinos-Users] sample makefiles


I've been primarily using trilinos in conjunction with sundance, but I am
interested in using it separately. Is there such a think as a generic
trilinos makefile for using the libraries and their dependencies?



-Gideon Simpson
Department of Applied Physics and Applied Mathematics
Columbia University



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://software.sandia.gov/mailman/private/trilinos-users/attachments/20070421/73b97497/attachment.html