	----- S-Lang README file and installation instructions ------

If you wish to be on the S-Lang mailing list, simply send me an email with
your email address.  I use the mailing list to announce new releases of
S-Lang and to report any bugs.  Send an email to:

davis@space.mit.edu

------------------------------------------------------------------------------
Installation instructions.

Building the S-Lang library requires a C compiler that understands function
prototypes.  On SunOS, you will need gcc.

S-Lang has been successfully compiled and tested on many platforms and OSs
(Unix/VMS/PC-MSDOS/OS2).   There are at least 4 makefiles included in the
distribution:

     makefile.unx    Unix (See note below)
     makefile.dos    MS-DOS (Borland BCC specific)
     makefile.os2    OS2 makefile
     makefile.djg    DJGPP (GO32) specific
     vmsmake.com     VMS DCL command procedure
     deccmake.com    Use this for the DEC ALPHA
     
As usual, look at the relavent makefile and edit it as required for your
system.  On VMS, just type `@vmsmake' or if you have gcc, type `@vmsmake gcc'.
For VMS ALPHA systems with DEC C, use `@deccmake'.

For non-VMS systems, copy the appropriate makefile.xxx to `makefile'.  Then
after editing it, simply type `make'.

The library comes with a sample program called calc.  Once you have
successfully built the S-Lang library,  simply type `make calc' to build the
sample application.  This step is not necessary if you are running VMS.

Also to browse the online documentation, create the help file reader in the
help directory.

Finally not that some Unix systems do not have `ranlib'.  If you see an
error indicating this fact, simply ignore it.

**** Note on Unix makefile (makefile.unx)

makefile.unx is no longer compatable with old-fashioned make programs.  It
is known to be compatable with GNUmake and the SunOS make.  If you have an
old make, use makefile.old; however, since I do not plan to continue
supporting makefile.old, you will definitely want to install GNUmake at some
point.

The new makefile is designed to ease the maintainance of the slang library
(and programs that use it) on systems where multiple architectures are
supported.  It works by putting the compiled object files and the resulting
library in a separate, system architecture dependent directory.  This
directory is specified by the OBJDIR variable and the default setting is

OBJDIR = $(ARCH)objs

Here, ARCH is a variable which has no default value.  It is assumed to be
defined by an environment variable, e.g.,

    setenv ARCH `arch`         # csh, tcsh
    ARCH=`arch`; export ARCH   # bash
    
For example, on my linux system, the arch command returns `i586' which means
that OBJDIR gets set to `i586objs'.  If ARCH is not defined, OBJDIR will be
set to the value `objs'.

