INSTALLATION.rtf
LGDCommunicationKit, Release 1.0 (prerelease)

Copyright (c) 1993, Looking Glass Design, Inc.
All rights reserved.

Project Manager:	Paul Girone
Original Author: 	Mike Gobbi
Creation Date:	June 30, 1993

$Revision: 1.1 $

Installing the Kit

Installing the Looking Glass Design Communication Kit is a straightforward matter.  Simply read and follow the instructions below, or, if you are the sort of person who never bothers with instructions, simply enter
	% make
on the command line.

Where it is installed

By default, the following installation targets are used:
	Header files		/usr/local/include
	Library			/usr/local/lib
	Palette			/LocalDeveloper/Palettes
	Documentation	/LocalLibrary/Documentation
	Examples		/LocalDeveloper/Examples
If you wish to install the package differently, edit Makefile appropriately.

Installation Tools

By default the following unix tools are used
	/bin/mkdirs		Used to create directory paths
	/bin/cp			Used to transfer files
	/bin/ranlib		Used after copying library to update table of contents
	/bin/tar		Used to transfer directories
If you wish to use different tools, again you must edit Makefile appropriately. 

Performing the installation

From the command line (and in the same directory as this document), execute
	% make install
If the installation target directories do not exist, then they will be created.  Some kit-specific subdirectories will be created in the installation directories, and the kit contents will be copied to the appropriate locations.

If you wish, you can follow the installation with
	% make chown
to change the ownership of the newly-installed files.  By default, the ownership is chaned to root.  If you wish a different owner, you must edit Makefile before executing the make command.

Needless to say, it is necessary to have write-permission to the appropriate files in order for the installation to work.  If you want to change file ownerships, you will have to run the make while logged in as root.

De-installing the kit

From the command line (and in the same directory as this document), execute
	% make deinstall
This will remove any kit-specific files and directories, but will not remove the installation targets listed above in where it is installed.

Again, appropriate write permissions are required.