Cookbook for Building CalTrans and Standalone ONETWO

The following procedures, for building CalTrans and standalone ONETWO within the CalTrans environment, have been tested successfully on the three CalTrans-capable systems in the GA Fusion Group: hydra (running HP-UX), cardea (running Tru64 UNIX) and taurus (running Linux). You cannot assume that these procedures will work on any other computers.

One-time setup procedure:

Ensure that you have the proper .caltrans file in your HOME directory. You can download it from here:
```
      ftp://lithos.gat.com/pub/freemanj/.caltrans
```
by clicking on the above link, or from the command line by issuing these commands:
```
      cd
      wget ftp://lithos.gat.com/pub/freemanj/.caltrans
```
provided you have wget installed.
Set environment variables:
```
      source ~/.caltrans
```
Go to a directory where you want to work:
```
      cd /any/where/you/want
```
Check out (the latest version of) the CalTrans source tree:
```
      cvs checkout caltrans
```
Go down one level:
```
      cd caltrans
```
Make the makefiles by running this script:
```
      MMF
```
Make CalTrans, saving screen output to a log file:
```
      gmake World |& tee caltrans-build.log
```
Go to the ONETWO part of the CalTrans tree:
```
      cd onetwo/onetwo
```
Copy the (generated) include files from the directory below:
```
      cp -p [A-Z]????/*.i .
```
Make (debug version of) standalone ONETWO, saving screen output to a log file:
```
      gmake DEBUG=yes -f makefile_sa |& tee onetwo-build.log
```

The above procedure in compact form (for grabbing with your mouse):

cd
wget ftp://lithos.gat.com/pub/freemanj/.caltrans
source ~/.caltrans
cd /any/where/you/want
cvs checkout caltrans
cd caltrans
MMF
gmake World |& tee caltrans-build.log
cd onetwo/onetwo
cp -p [A-Z]????/*.i .
gmake DEBUG=yes -f makefile_sa |& tee onetwo-build.log

Development procedure:

Make sure you are in the directory where you performed the last step above.
Make sure you are up to date:
```
      cvs update
```
Start editing some source code, for example:
```
      xemacs crayAAA.f crayBBB.f &
```
Make (standalone) ONETWO, in debug flavor most likely:
```
      gmake DEBUG=yes -f makefile_sa
```
Run the (standalone) ONETWO you just created:
```
      ./onetwo
```
Check back in your changes if you are convinced that they are good:
```
      cvs commit crayAAA.f crayBBB.f
```

Important note: The above development procedure assumes you will only be changing .f files, not .i files. If you will be changing the latter, there are important additional steps that must be taken.

This page http://fusion.gat.com/THEORY/caltrans/cookbook.html was updated Thursday, 7 February 2002 at 07:12:38 PM.