![[CLISP home]](clisp.png){kind=small} | ![[Support CLISP]](http://images.sourceforge.net/images/project-support.jpg){kind=small} |
clisp-link [create] [modulefile
clisp-link [add] [sourcedestinationmodule
clisp-link [run] [sourcemodule
This shell script operates on CLISP module sets and linking sets:
creates new module sets out of
source filesadds module sets to a linking set to produce a
new linking setruns CLISP with module sets added
createThe command
$clisp-linkcreatemodulefile...
creates a module set in module directory which refers
(via symbolic links) to files file...
The files are expected to be modules of their own.
addThe command
$clisp-linkaddsourcedestinationmodule...
combines the linking set in directory source and the modules in
directories module... to a new linking set, in the directory destination
which is newly created.
runThe command
$clisp-linkrunsourcemodule...
runs the linking set in directory source, with the modules
in directories module...
Unless CLISP has been built with the configuration option
--without-dynamic-modules, the loading will be performed using SYS::DYNLOAD-MODULES.
Otherwise - this is much slower - a temporary linking set will be created
and deleted afterwards.
clisp-link needs a “link kit” directory containing:
"modules.c""clisp.h" clisp-link expects to find these files in a
subdirectory linkkit/ of the installation directory
(i.e., CUSTOM:*LIB-DIRECTORY*) which it acquires by running
$`dirname $0`/clisp-b
This can be overridden by the environment variable CLISP_LINKKIT.
| |