Copyright (C) 1996 Peter Kabal

The AFsp audio file routines are provided free of charge without warranty of
any kind.  All components are copyrighted.  They may be distributed free of
charge provided that the recipients also acquire the right to distribute them.
In no case can this software be incorporated into a work which is distributed
for a fee.

Building libtsp.a:
  After unpacking the sources, go into the libtsp directory.
  % cd libtsp
  % make
  This will build the library file lib/libtsp.a.

Building the utility programs:
  Return to the main directory, then go into the audio directory.
  % cd audio
  % make
This makes the programs CompAudio, CopyAudio, FiltAudio, GenNoise and
InfoAudio.

Test script:
  In the directory test, there is a test script which will exercise several of
  the audio utility programs.  A sample output is in the file txxxAudio.ref.
  tFiltAudio.ref.
  % cd test
  % txxxAudio | filter_log > tA.log
  % diff tA.log txxxAudio.ref

Using the library routines:
  To use the AFsp routines in a program you will have to link with the
  object library libtsp.a.  Furthermore, user programs need access to the
  header file libtsp.h.  I suggest putting libtsp.a (or a link to it) in
  /usr/local/lib and libtsp.h (or a link to it) in /usr/local/include.

Man page files:
  The directory man contains man pages for the utility programs and the top
  level libtsp routines.  These man pages have been automatically generated
  from the corresponding file header and so contain the same information as the
  file header itself.  The extensions for the man pages are .1audio and .3tsp.
  On some systems, these will have to be renamed to .1 and .3 in order for the
  man program to recognize them.

Other files:
  A number of routines are hidden one level down in a "nucleus" directory.
  These are internal routines usually not of interest to the end user.

  A number of audio files of various formats can be found in the
  test/audiofiles directory.

  The header files in the include/libtsp directory are used to define internal
  data structures.  While not usually used directly by the end user, these
  header files should be available, particularly for rebuilding the library.
  These might find a home in the directory /usr/local/include/libtsp.

Systems:
  The AFsp routines have been built on the systems listed below.  Extensive
  testing has been carried out for only the first three configurations listed.
  - SunOS 4.1 running on a Sparc machine (cc, acc, CC and gcc compilers)
  - Irix 5.2 running on a SGI Indy (cc and gcc compilers)
  - DEC Ultrix 4.x running on a DECstation (mips cc and gcc compilers)
  - SunOS 5.4 (Solaris) running on a Sparc machine (cc and gcc compilers)
  - OSF/1 V1.3 running on a DEC 3000 Model 300LX (cc compiler)
    The standard make for this system does not build libtsp.a.  It will build
    the object files; these then have to be put into the archive manually.  Gnu
    make works as desired.
  - HPUX 9.01 running on a HP 735 (cc and gcc compilers)
  - MS-DOS running on a PC-386/486 (MS Visual C++ and djgpp gcc compilers)
    For MSVC: use /Za and the Large memory model as compiler options; stack
    size 34000, 256 segments, and /NOE as linker options.

$Id: INSTALL,v 1.19 1996/07/16 AFsp-V2R1 $