In order to install GLE on a UNIX system ftp the following files:

Be sure to use binary transfer for tar_z files.

	$ ftp wuarchive.wustl.edu 128.252.135.4
	FTP> user anonymous
	Password: (your Email address)
	FTP> cd /graphics/graphics    (probable directory, check index)
	FTP> ascii
	FTP> get gle33a.txt		(this file)
	FTP> binary
	FTP> get gle33a.tar.Z
	FTP> get gle33a.ps.tar.Z  (Optional PostScript copy of manual)
	FTP> quit
	
.............................................................................
GLE will compile under GCC or XLC (on AIX R6000's) 

It is suggested that you build GLE in a temporary directory of it's own
and then use the install.sh script to copy the 'required' parts
of gle into the system areas, you can then delete the gle source directory
tree.

Then uncompress and un-Tar the installation kit.
	uncompress gle.tar.Z
	tar -xvf gle.tar
	cd gle

GLE needs to know where it is being built as it runs itself during
the installation.  Define GLE_TOP:

(sh)	. path.sh
(csh) 	source path.csh

To test SURFACE you will need to define SURF_TOP too.

	export SURF_TOP="/home/mydir/gle/util/surf/"

	(THIS is done inside path.sh)
	
These defines are not needed once gle is installed in the system directories.

If you are going to want to test it before copying it to /usr/local/bin
then you might want to add GLE_TOP into your PATH.

	export PATH=$PATH:/home/mydir/gle

It might be worth touching the files as TAR doesn't always 
get the dates right (which confuses make):
	touch gle/*
	touch gle/*/*
	touch gle/*/*/*
(if you are  building gle in a directory which already had a copy of 
gle then you might have to force make to recompile by deleting the
object files.
	rm *.o
)

Pick one of the files {config.*} which most matches
your machine and copy it to {config.i}, you may want 
to edit this file if you have xwindows or need to make 
some other simple change.

	ls config.*
	cp config.ultrix config.i

Now run make:
	make
Once that has completed type in:
	make doutils

To test gle out:
  Create yourself a gle directory to play in:
	mkdir gletest
	cd gletest
	cp ../demo/*  ( or /usr/local/gle/demo/*   to copy the examples)
	
  Then try it out (note: the command is gle, not cgle):
	../gle test.gle 		(For dumb terminals)
	../gle test.gle -dX	(For xwindows)
	../gle test.gle -dtek	(Tektronix 4010 terminals)
	../gle test.gle -dregis 	(Regis, vt240, vt340)
	../gle test.gle -dhpgl  	(HP plotters)
	../gle test.gle -dps	(To produce PostScript output)

(NOTE: if you already have gle installed in a system path then
the old version of gle will be picked up rather than the new version
 (even using gle_path).  To avoid this problem you should temporarily 
remove gle from your path variable, you can also run specific
gle drivers using:
	../gle_ps  (PostScript)
	../gle_vt  (terminal)


	(You must replace ../ with the path to where the gle executables
	were created)

	(To load a different example press ^F 3, then ^F 0 to draw it)

To install gle executables in /usr/bin and the gle help,font and example
files into /usr/local/gle enter the command:
	install.sh

If you wish to install gle in a different directory permenently 
then you can modify the file {glepath.h} and then recompile or 
you can use the environment variable GLE_TOP

After checking that gle is working correctly you can delete
the source files to save a lot of space:
	cd ..
	rm gle -r		

Once gle has been installed the commands that are added are:

	gle		Graphics Language Editor, graphs and slides.
	surface		Plots hidden line wire mesh 3d plots
	fitls		Fit's best fit least squares line to any equation
	fitz		Creating even grid data from random xyz data
	letz		Creating grid of values from expression
	manip		Data manipulation

There is a postscript and text only copy of the manual in the directory
	gle/manual/
		gle.ps
		gle.txt
		util.ps


If you have to make changes to install GLE on your machine please
send them to me.

				Thanks,  Chris.  (srghcxp@grv.dsir.govt.nz)








