This is the INSTALL file for the version 2.0 of FElt.

If you grabbed a binary release (available for Linux, HP-UX and SunOS) then
all you need to do is the "make install".  The install prefix should be
/usr/local as a couple of the pre-compiled applications will look for files
in /usr/local/lib/felt.  The binaries should be FElt/bin/Felt/felt,
FElt/bin/Velvet/velvet and FElt/bin/XFelt/xfelt.  If you are doing a build
from source or need to change the built-in pathnames, read on ....

First, read the README file.  You need a C compiler and X11R5 (including the
Athena widget set) to compile FElt.

Second, cd to the root of the hierarchy (./FElt) and do a "make config".
This will ask you various questions about your system and create a new
"Makefile.conf" file.  Each time you do a "make config", the configuration
script will use your old responses as the default answers.

You'll no longer be asked questions concerning your Fortran compiler.  We
found that too few people had a Fortran compiler and those that did have a
compiler could not easily determine what their Fortran libraries were.  If
you still wish to use a Fortran compiler, edit the "Makefile.conf" file by
hand afterwards.  The geompack library used for element generation is written
in Fortran but C versions as converted by f2c are provided.  Using a native
Fortran compiler is recommended since it will probably outperform the
corresponding C code, but unfortunately determining what your specific
Fortran libraries are is not a simple process so unless you know exactly
what you are doing it's not worth bothering with.  You don't need to have the
f2c libraries to use the converted code.

The remainder of the questions should be relatively straight-forward.
Afterwards, you can edit the "Makefile.conf" file by hand if you need to.
The entire package has been compiled and tested under SunOS (using gcc),
HP-UX 8.0 and 9.0 (using HP's cc and gcc), and Linux.  Earlier releases 
compiled and ran on SystemV386 (R3.2.2 using gcc), various SGI machines,
and DEC (using both OSF/1 and Ultrix) and IBM (AIX) workstations.  There is
no reason this one shouldn't do the same.  

Note that if you're using gcc, make sure that you use gcc's include files and
not the system's include files.  This shouldn't be a problem unless you put
something like "-I/usr/include" in your compiler flags.  Gcc has its own
ideas as to how some things like variable argument lists work.  For example,
if you get the wrong "varargs.h" file included then the diagnostic and error
messages will either report obviously incorrect values or will cause a core
dump.

Next, do a "make clean" followed by a "make all".  To install the package do
a "make install".  This will copy the binaries and manual pages to the
specified directories.  If you do not do a "make install" you will need to go
into each individual directory off of FElt/bin to play with the applications.
The test suite is located in FElt/etc/Tests/*.flt.  A simple test of the
build before installation would be to cd to FElt/bin/Felt and execute "felt
../../etc/Tests/mixed_dist.flt".  Compare that with the original output in
../../etc/Tests/mixed_dist.ans.  Now go into FElt/bin/Velvet and execute
"velvet ../../etc/Tests/mixed_dist.flt".  The drawing area should display a
T-shaped structure. Selecting solve from the problem menu should result in an
output window with the same answers as before.

We personally prefer the 3d Athena widget set; if it's available on your
system and you want to use it, the only thing we recommend that you change
are the app-defaults ... simply uncomment the 3d stuff in the file Velvet.ad
in the bin/Velvet directory (and comment the 2d stuff).

Additional information about building and administering is available in
Appendix A of the User's Guide and Reference manual (available separately).
You'll definitely want to read this if you plan on installing and actively
using the system.
