Node:Runtime Systems on Target Machines, Next:The Application Builder, Previous:Runtime Systems, Up:Stand-alone Executables
When a runtime system is delivered to the end user, chances are that the user does not have an existing SICStus installation. To deliver such an executable, you need:
spld
(see The Application Builder).
$SP_PATH/../libsprt39.so
under UNIX, or
%SP_PATH%\..\sprt39.dll
under Windows.
$SP_PATH/bin/sprt.sav
contains the built-in
predicates written in Prolog. It is restored into the program at
runtime by the function SP_initialize()
.
Extended runtime systems restore $SP_PATH/bin/spre.sav
instead,
available from SICS as an add-on product.
.po
files, .ql
, or source code
(.pl
files). They must be explicitly loaded by the program at
runtime (see Loading Prolog Code).
$SP_PATH/library
.
See UNIX Runtime Systems on Target Machines, for more information about runtime systems on UNIX Target Machines. See Runtime Systems on Target Machines, for more information about runtime systems on Windows Target Machines.
It is also possible to package all the above components into a single executable file, an all-in-one executable. See All-in-one Executables.