Software Tools for DAKOTA Development

Software Tools Table of Contents

Introduction

DAKOTA development relies on Subversion for revision control and the GNU Autotools for configuration management. This section lists these tools, where to acquire recommended versions, and how to configure them.

Subversion for Version Control

The DAKOTA project uses Subversion (http://subversion.tigris.org/) for software version control. To check DAKOTA out of the Subversion revision control system on development.sandia.gov, it may be necessary to install or upgrade the Subversion client on your system. We are presently using version 1.3.2 available from http://subversion.tigris.org/downloads/subversion-1.3.2.tar.gz.

To configure and build Subversion from source on your machine, the following settings should be used, since DAKOTA is hosted as a FSFS-type repository and depends on the external acro which is stored in a repository requiring SSL certificate handling:

tar xzf subversion-1.3.2.tar.gz
cd subversion-1.3.2
./configure --prefix=$HOME/local --with-ssl --without-berkeley-db CFLAGS=-O2
cd neon
./configure --prefix=$HOME/local --enable-shared --with-ssl --without-berkeley-db CFLAGS=-O2
cd ..
make && make check && make -k install

The make command as specified will ensure that Subversion is only installed if it passes all its self-tests, as well as making sure that the client install works correctly. Under some conditions, the Subversion build will attempt to write to /usr/lib, even when a --prefix option is passed to ./configure. This error may be disregarded when building the Subversion client, hence the -k option.

Once Subversion is working, DAKOTA (including externals) can be checked out with the single command

svn checkout svn+ssh://development.sandia.gov/usr/local/svn/Dakota/trunk Dakota

If you experience server timeouts when SVN attempts to fetch external packages through a proxy server, you might need to make a change to your $HOME/.subversion/servers file (generated for you the first time you run svn) by adding

[global]
http-proxy-exceptions = localhost, *.intranet.mydomain.com
http-proxy-host = wwwproxy.mydomain.com

to the bottom of the file. You should no longer get server timeouts when getting acro from software.sandia.gov. If you find that checking these three packages out from software is unacceptably slow, you may add your hostname to the end of the http-proxy-exceptions line. Finally, svn will prompt you as to whether you wish to accept the SSL certificate from software; type 'p' for permanent.

To set the default editor for Subversion commits, you may add the following to .cshrc:

  setenv EDITOR "xemacs -g 81X50"

GNU Autotools for Configuration Management

DAKOTA uses the GNU Autotools (http://www.gnu.org/software/autoconf/) for configuration management. Developers are currently using the following versions:

  1. m4-1.4.3 (http://ftp.gnu.org/gnu/m4/m4-1.4.3.tar.gz)
  2. libtool-1.5.24 (http://ftp.gnu.org/gnu/libtool/libtool-1.5.24.tar.gz)
  3. automake-1.9.6 (http://ftp.gnu.org/gnu/automake/automake-1.9.6.tar.gz)
  4. autoconf-2.60 (http://ftp.gnu.org/gnu/autoconf/autoconf-2.60.tar.gz)

Building the tools in the order listed above should satisfy dependencies. For each PACKAGE the following build process should suffice:

tar xzf $PACKAGE.tar.gz
cd $PACKAGE
./configure --prefix=$HOME/local
make
[make check]
make install
(Make check is useful for debugging builds of these packages, but optional and does take considerable time for some packages.)
Generated on Wed Nov 5 19:54:04 2008 for DAKOTA by  doxygen 1.5.1