README -- 6/94

Greetings and welcome to mixview.

This program is currently designed to run under Sun OS 3.2, 3.4, and 4.0, and
should be totally compatible with all BSD Unix machines.  The lxt toolkit has
separate makefiles for the various Sun OS releases -- consult the documentation
in the toolkit release, as you may need to make minor changes to reflect your
system.  Additional changes have been made to allow mixview to compile on an
IBM 386 machine and on SGI platforms.

The lxt source code should be untarred in a separate directory from the
mixview source code, and the mixview Makefile should be edited to reflect the
location of the lxt source (see the Makefile).

Building Mixview on Different Machines:

The only system-dependent portion of the editor is the code relating to 
D-to-A conversion of soundfiles.  It is compatible with with D-A converters
on NeXTs, SPARC I, and SPARC 10 workstations that have the optional SOUND 
package (library and include files) installed.
Two new converters are now supported:  the SoundBlaster, used on IBM 386
machines, and the Audio Controller Board from Audio Digital Systems.
The program will compile without errors, however, on any machine without
changing the conversion code.  I would be delighted to hear of other drivers
capable of converting from memory so that I may add options for them in mixview.

NEW NOTE:  This program will also compile on SGI machines and use the AGI
audio hardware, and will read AIFF format sounds.  You will need to apply the
supplied patch file to the lxt source code to compile it.

Here are some guidelines on how to set the compiler options in the mixview
Makefile.

FLAGS=	Set this one to a typical set of flags for the c compiler on your
machine (e.g., -O).  Several samples are included.

SYSLIBS= Set this according to your system (see Makefile).

LXTMAKEOPTS= This determines which Makefile will be used to build the LXT
toolkit.  It should be set on all machines other than Sun4s, which use the
default makefile.  Examine the available Makefiles in LXT if you are not
sure.

COMMENTFLAGS= This is set to -DHAS_SFCOMMENT on all machines except those that
use the Ircam soundfile header without comment space. (Very few of these).

DACFLAGS= This is set depending on the D-to-A converter used on your machine.
All available options are given the the Makefile.  Only set one!  If your
machine has no DACs, set it to nothing.

DACINCLUDES= This is currently used only on machines using the Audio Digital
Systems converters.

SNDFLAGS= This determines what type of soundfile headers and header routines
will be used.  It is most important on Sun Sparcs using the Sparc soundfile
headers [-DSPARC_AUDIO], or on machines that wish to read NeXT header format
files [-DUSE_NeXT_HEADERS].  This can only be done if you have a copy of the
NeXT soundfile header files from the include/sound dir on a NeXT.

SNDINCLUDES= On Sparc machines, this need to be set to -I<dir> where <dir> is
the directory containing the header files for sound.  If you are working on a
Sparc and wish to read NeXT format files, set this to the dir containing your
copy of the NeXT header files.

FORTDEFINES= Set this depending on whether your machine has a Fortran compiler
[-DHAS_F77] or has the f2c libraries [-DHAS_F2C] or neither [leave blank].

FORTFLAGS= Set this to -lF77 or -lf2c depending on your configuration, as
above.

NOTE:  Farther down in the Makefile is a target for setell.o.  This must be
set to match the fortran configuration as well.

There may be other smaller adjustments to the Makefile, such as the options
for the X11 inclusions and libraries.  Examine the Makefile for such things if
you are having problems.

-------------------------------------------------------------------------------
NOTE:  You must use the newest release of LXT with this release of mixview.
There are changes that are not compatible with the old toolkit.  As the author
of mixview, I do not have the authority to issue the additional changes that
may be needed to compile LXT on other machines.  Send me mail if you have
problems.
-------------------------------------------------------------------------------

Once the toolkit and this source code are unpacked and un-tarred and after
modifying the makefile in the top level, simply type 'make' at the top-level
directory, and then 'make install'. 

Douglas Scott
doug@foxtrot.ccmrc.ucsb.edu