This file contains installation information for the Sather Xlib
interface.  If you have questions concerning this file or the library,
mail to <schnetter@student.uni-tuebingen.de>.  This text was last
updated on 1994/12/09.



INSTALLING:

The classes come in a whole bunch of files, instead of in one file
only.  This accelerates compiling, as normally not all of the files
have to be parsed.  You should copy all these files into one
directory.  In the following I assume that this is the directory
'/home/user/Sather/Library/Xlib'.

The Xlib interface classes use C code, too.  Before you can use it,
you have to compile it.  This is best done via

	cd /home/user/Sather/Library/Xlib
	make

If this fails, or if you don't have a make utility, you can do it by
hand:

	cd /home/user/Sather/Library/Xlib
	cc -c -O -g *.c
	ar rc xlib.a *.o
	# (if you don't have ranlib, then you probably don't need it)
	ranlib xlib.a
	# and to save some space:
	rm *.o



In order to use this interface, you have to tell the compiler by
adding '-com /home/user/Sather/Library/Xlib/xlib.commands' to the call
of the compiler, as in

cs program.sa -o program -main PROGRAM
-com /home/user/Sather/Library/Xlib/xlib.commands

(but in one line!)

This is tedious.  A more convenient way to do so is to add this to
your environment variable SATHER_COMMANDS.  Assuming you set this
variable already to

-home /home/user/Sather -com /home/user/Sather/Library/base.commands

then you should instead set it to

-home /home/user/Sather -com /home/user/Sather/Library/base.commands
-com /home/user/Sather/Library/Xlib/xlib.commands

(again, in one line!).  Having done this, you can compile with

cs program.sa -o program -main PROGRAM

and then the Xlib classes are parsed automatically whenever a program
of yours uses them.



-erik
