Dear clisp developers,
I just added a "direct executable" feature to cl-launch 2.0, to
produce "standalone" executables instead of a script that relies on
either sources or an external dump.
I found myself unable to get this feature working with clisp, because
clisp insists on parsing options. Could it be possible to apply the
parse-options patch by Klaus Grue GRD-2006-03-09, or something
The :script option doesn't cut it.
As for the solution to problem (7) in said email, I'd say that
ideally, clisp would be able to open an executable file with option
-M, thus allowing to execute it with parsed options. But that's a more
complex task indeed.
Note SBCL and GCL executables seem to have the same issues. I could
only get this cl-launch feature to work with ECL at this time.
[ Fran=E7ois-Ren=E9 =D0VB Rideau | Reflection&Cybernethics | http://fare.tu=
Time and money spent in helping men to do more for themselves is far better
than mere giving. -- Henry Ford
back in October 2006, I reported that I did not manage to use
unpatched clisp to build standalone executables, because executables
built with clisp would always treat specially such options as -M, -x,
-norc, etc., without giving control to the user.
Klaus Grue had a solution to this problem, but it was never merged
into clisp (that I know).
Could this solution (or something similar) be merged into the next
release of clisp? (and once again, :script t doesn't do it).
I'm rolling out a new version of cl-launch, and it currently supports
standalone executables with SBCL, ECL (when that works - bugs with
asdf) and LispWorks. It would be nice if I could support CLISP, too.
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
This sequence of glyphs is provided AS IS. Any interpretation of it in terms
of meaningful statements is left to the sole responsibility of the reader.