There are four sample configuration files in LispWorks library containing settings you can change in order to configure images:
config/configure.lisp
is preloaded into the image before it is shipped. It contains settings governing fundamental issues like where to find the LispWorks runtime folder structure, and so on. You can override these settings in your saved image or in your initialization file. You should read through
configure.lisp
.
config/siteinit.lisp
contains any forms that are appropriate to the whole site but which are to be loaded afresh each time the image is started. The sample
siteinit.lisp
file distributed with LispWorks contains only the form:
(load-all-patches)
On startup, the image loads
siteinit.lisp
and your initialization file, in that order. The command line options
-siteinit
and
-init
can be used to specify loading of different files or to suppress them altogether. See the example in Saving and testing the configured image, below, and Initializing LispWorks for further details.
private-patches/load.lisp
is loaded by
load-all-patches
, and should contain forms to load any private (named) patches that Lisp Support might send you.
config/a-dot-lispworks.lisp
is a sample personal initialization file. You might like to copy this into a file
~/.lispworks
in your home directory and edit it to create your own initialization file.
Both
configure.lisp
and
a-dot-lispworks.lisp
are preloaded into the image before it is shipped, so if you are happy with the settings in these files, you need not change them. See the example in Saving and testing the configured image, below, and Initializing LispWorks for further details.
LispWorks Release Notes and Installation Guide - 23 Dec 2011