There are four files in the LispWorks library containing settings you can change in order to configure images:
config/configure.lisp
contains settings governing fundamental issues like where to find the LispWorks runtime directory structure, and so on. You should read through
configure.lisp
and check that you are happy with all the settings therein. The most common change required is to
*lispworks-directory*
, which points to the root of the installation hierarchy.
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
file distributed with LispWorks contains only the form:
(load-all-patches)
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
.lispworks
file. You might like to copy this into your home directory and use it as a basis for your own
.lispworks
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.
On startup, the image loads
siteinit.lisp
and your
.lispworks
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 see also LispWorks initialization arguments for further details.