READ THIS before clicking on anything in this directory!
=========

This directory contains assorted scripts and lisp fragments for
creating standalone images and saved state versions of KPML.

In general one needs to edit only the path information in these
scripts for them to work appropriately. Most, if not all, of
these are for Lispworks, as Franz is more restrictive about
who you can make images for and how much they want to charge
you for it.

The scripts are provided AS IS, without guarantee (i.e., even
less than usual). You should probably be generally familiar
with the process of making images and standalones under
Lispworks before playing with these. You should also
have been able to install KPML from the sources up to and
including the loading of resources and generation of examples--
otherwise whatever went wrong then will go wrong again when
the script is run, but without much possibility of you
being able to find out what it is that is failing.

The *.bat files start up Lispworks and run the corresponding
Lisp file for possibly compiling, loading and freezing the
KPML image required. They are quite good when everything
works since they reduce the work of making images to
a mouseclick. The created images are saved to C:\tmp
unless you change this bit of the *lisp* file used 
by a script. Naturally they can also be changed so that
grammars in various stages of development are similarly
'frozen' into the image created.

John Bateman
Bremen, September 2002

---------------------------------------------------------------------------------
The following comments generally hold for all the image
making bat files when they run:

;; ----------------------------------------------------------------------
;; INSTRUCTIONS FOR USE...
;;
;; The startup dialog must be answered as usual
;; but in a DOS-style interaction popup window. 
;;
;; The first place where user interaction is required is to answer
;; the question: 
;; (1) Compile KPML? 
;;    If this is a fresh installation and an image is being made, and
;;    if it can be assumed that KPML is going to compile without difficulties
;;    (which any freshly downloaded release files should do), then one
;;    can also simply compile KPML at this stage too: 
;;    In this case and only this case answer: 'y' followed by carriage return.
;;
;;    Otherwise KPML should already have been compiled in order to check that
;;    it is working, so we should not recompile it here:
;;    answer `n' followed by a carriage return.  
;;
;; (2) Then the next question
;;     should appear: Load KPML? 
;;     which should always be answered `y' followed by
;;     a carriage return. Loading then proceeds as normal... 
;;
;; (3) The safest answers to the configuration questions are as always: 
;;       y to load clim interface,
;;       n to load linguistic resources,
;;       y to load upper model,
;;       n to load general inquiry implementations.
;;
;; If things are in this file have been localized appropriately, it
;; should run through until an image is saved without further interaction.
;; The final image for an empty KPML image occupies around 32Mbyte.
;;
;; ----------------------------------------------------------------------
