The command line used to run LispWorks can be found using the variable
*line-arguments-list*. The value is a list of strings containing the executable name followed by any other command line arguments, in the order they were passed.
For example, if your application needs to behave differently when passed an argument
-foo, use the following test:
(member "-foo" sys:*line-arguments-list* :test 'string=)
build-script can name a file to be loaded on startup. This file will be the build script which loads your code and calls save-image or deliver. LispWorks quits after loading the file. If an error is signaled while loading the file, a backtrace is displayed and LispWorks quits.
build-script can also be
-, a single minus sign. Passing
-build - causes LispWorks to read and execute a build script from stdin. This is useful if you want to embed a build script within a shell script that runs LispWorks, for example:
An image run with
-build runs itself, and not the default saved session if you created one. See Saved sessions for information on saved sessions.
Start the LispWorks IDE development environment automatically, even in an image saved with
(save-image ... :environment nil)
Evaluates the Lisp form form before loading initialization files.
If form requires multiprocessing, then change it to push a process specification onto *initial-processes*. This will delay evaluation until multiprocessing has started, either by the
-multiprocessing command line options or because LispWorks was saved to start multiprocessing.
A synonym for
init-file names a file to be loaded on startup after siteinit-file. The file is user's own LispWorks initialization file, containing code that by default is loaded when LispWorks is started. It is useful for loading initializations that should not be done for all users.
Initially the default is to load the file
"~/.lispworks" where ~ expands to the user's home directory as described in Configuration and initialization files.
Loads the file file before loading initialization files.
Makes the supplied image run itself, and not the default saved session if you created one. See Saved sessions for information on saved sessions.
Initializes multiprocessing on startup. See Multiprocessing.
Suppresses the execution of a restart function on startup. Restart functions can be supplied when saving an image to automatically invoke application code. This argument suppresses that behavior. See save-image.
Causes the image to relocate at BaseAddress on supported platforms, as described in Startup relocation. This can be useful on a system where libraries are mapped in address space that LispWorks would otherwise use as it grows. If the image is saved, then on restart without
--relocate-image, it will locate itself automatically at BaseAddress.
In LispWorks 5.0 and earlier versions, to be effective,
--relocate-image must be the first argument on the LispWorks command line. This restriction does not apply in LispWorks 7.1.
Specifies the reserve size on supported platforms, as described in Startup relocation.
siteinit-file names a file to be loaded on startup. The file is the LispWorks site initialization file, containing code that by default is loaded when LispWorks is started by any user in that installation. The default is to load the file that is the result of evaluating
Use environment-variable get and set the value of an environment variable in the environment table of the OS process that called LispWorks.
(setf (lw:environment-variable "FOO") nil)
LispWorks User Guide and Reference Manual - 20 Sep 2017