3.1 Configuring Liquid Common Lisp software

3.1.1 Setting the lispworks-directory variable

Normally this parameter is automatically set up as the base image starts up and attempts to configure itself. It does this by assuming that the unconfigured base image is being executed from the place in the installation directory hierarchy in which it was originally installed. From the path of the actual running image, it can figure out where the rest of the hierarchy should be.

There are some manual steps which you can take in order to force the selection of the directory. Note: you must take one or the other of the following steps if you move or copy the unconfigured image from the place where it was originally installed to another location and attempt to execute it from there.

Set the shell environment variableLISPWORKS_DIRECTORY to the ~installation_directory/platform/ before starting up the image,
Make a symbolic link from/usr/lib/lispworks to the directory ~installation_directory/platform/ (this pathname is a "fall back" choice of last resort, even if the directory does not actually exist), or
After starting up Lisp (again, with the-n command line flag), set the Lisp global parameter*lispworks-directory* to the pathname#P"~installation_directory/platform" by hand.

Note that these steps are not necessary for an image that has been configured and saved withdisksave. But you may force the re-configuring of an already configured image by either:

Setting the shell environment variableLISPWORKS_DIRECTORY prior to starting up the saved image, or
Setting the Lisp global parameter*lispworks-directory* tonil just before callingdisksave.

Sometimes, users find that a large application runs faster when the executable image is stored on a local disk. Normally, such an application is the result of an extensive configuration such as described in this section (3.1), including thedisksave to a local disk file. However, there are circumstances under which you may find it necessary to move or copy an unconfigured Lisp image from its place in the ~installation_directory hierarchy onto a local disk. This is the primary reason that manual intervention by setting the*lispworks-directory* becomes necessary.

Liquid Common Lisp 5.0 Release and Installation Notes - 9 JUN 1997

Generated with Harlequin WebMaker

3.1.1 Setting the *lispworks-directory* variable

3.1.1 Setting the lispworks-directory variable