
 ;;
 ;; The Framework for Resolution-Based Automated Proof Procedure Systems
 ;;                         FRAPPS Version 2.0
 ;;    Authors: Alan M. Frisch, Michael K. Mitchell and Tomas E. Uribe
 ;;               (C) 1992 The Board of Trustees of the
 ;;                       University of Illinois
 ;;                        All Rights Reserved
 ;;
 ;;                              NOTICE
 ;;
 ;;   Permission to   use,  copy,  modify,  and   distribute  this
 ;;   software  and  its  documentation for educational, research,
 ;;   and non-profit purposes  is  hereby  granted  provided  that
 ;;   the   above  copyright  notice, the original authors  names,
 ;;   and this permission notice appear in all  such  copies   and
 ;;   supporting   documentation; that no charge be  made for such
 ;;   copies; and that  the name of  the University of Illinois or
 ;;   that  of  any  of the Authors not be used for advertising or
 ;;   publicity  pertaining  to   distribution   of  the  software
 ;;   without   specific  prior  written   permission. Any  entity 
 ;;   desiring  permission to incorporate   this   software   into
 ;;   commercial  products  should  contact   Prof.  A. M. Frisch,
 ;;   Department  of Computer  Science,  University  of  Illinois,
 ;;   1304  W.  Springfield Avenue, Urbana, IL 61801. The  Univer-
 ;;   sity of  Illinois and the Authors  make  no  representations
 ;;   about   the suitability  of this  software  for any purpose.
 ;;   It is provided "as is" without  express or implied warranty.
 ;;
 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;


Installation notes:

Directories: frapps (main directory): 	frapps source code
	     frapps/demos:		sample problem sets, proof procedures
	     frapps/hooked:		"hooked-on-FRAPPS" source code
	     frapps/hooked/hdemos:	hooked-on-FRAPPS demos

			***************

All the FRAPPS source and object files should be installed in the same
directory. The files that make up the extension of FRAPPS to constraint
unification, H-FRAPPS, are in the "hooked" subdirectory.

Some source files are shared between regular FRAPPS and the "hooked" version.
(This is noted in the file headers.) Compiled files cannot be shared between
the two, so there's two separate directories for each.

Normal frapps is loaded via the "init.lsp" file.
Hooked-on-frapps is loaded via the "hinit.lsp" file.
Global variables in these files define the directories where files should be.
In general, the h* files in the "hooked" directory are the counterparts
of normal FRAPPS files.

If something is changed in a regular FRAPPS file that is NOT shared,
the corresponding change should also be made in its counterpart h-FRAPPS file,
if applicable.

See the hooked/README file for more info on H-FRAPPS.

			***************

To make FRAPPS run at a particular location, the global variables
at the beginning of the file "init.lsp" should be changed.

The *bug-kcl* variable should be set to T if KCL is used due to a
bug in KCL's read-line facility (at the time of this writing).
The correct "interface behavior" of the (option-start-frapps)
and (run-demo) functions depends on this.
More importantly, the success of the session management functions may also
depend on this.

The other variables to be set describe the path to the frapps directory,
the demos directory, and the suffixes for interpreted and compiled
files (i.e. "xxx.lisp" vs. "xxx.lsp", ".sbin" vs. "bbin" vs. fasl., etc).
Note that these variables also appear in "hinit.lsp", so they should
be changed there as well if H-FRAPPS is also installed.

			***************

The function "compile-frapps" should be used to compile frapps after it
ALL has been loaded into the lisp environment using "start-frapps".

Currently, the two files that support the demos,
"user.lsp" and "run-demos.lsp", are included in FRAPPS (and H-FRAPPS).
In any case, "load-demos" loads the two files that make up the demos,
and "compile-demos" compiles them.

The compilation functions will only compile those files whose compiled
counterpart is not present in the object-file directory.
If non-trivial changes are made, it is recommended that all compiled files
be deleted and FRAPPS compiled again.
