Re:Using SBCL Common Lisp as a Dynamic Library
by lispm on Sunday April 17, 2022 @03:43AM
(#31059241)
> save a core image.
which can be made executable. So saving an image is the way to create an executable.
> the people developing it have little or no interest in those features
the demand for these features from the SBCL user base also does not seem high. If it would have been needed, then the development could have been sponsored, like for example the support for Apple Silicon was sponsored by users.
Though other CL implementations provide different deployment options:
ABCL compiles to JVM code.
ECL can compile to C or portable byte code. It also has been used for Android and iOS apps.
LispWorks & Allegro CL have treeshakers and can generate shared libraries. LispWorks also has a runtime for Android and for iOS.
which can be made executable. So saving an image is the way to create an executable.
> the people developing it have little or no interest in those features
the demand for these features from the SBCL user base also does not seem high. If it would have been needed, then the development could have been sponsored, like for example the support for Apple Silicon was sponsored by users.
Though other CL implementations provide different deployment options:
ABCL compiles to JVM code.
ECL can compile to C or portable byte code. It also has been used for Android and iOS apps.
LispWorks & Allegro CL have treeshakers and can generate shared libraries. LispWorks also has a runtime for Android and for iOS.