[cmucl-help] Command Line options in standalone executables

Raymond Toy toy.raymond at gmail.com
Tue Nov 2 18:33:48 CET 2010

On 11/2/10 12:56 PM, Didier Verna wrote:
> Raymond Toy <toy.raymond at gmail.com> wrote:
>> Fixed the problem. It was an issue with how the command line is parsed
>> when there are no other options besides --.
>   OK. Now, even with this problem fixed, it is still not clear to me
> whether it is possible to create executables in which all command-line
> options are in fact user-level.
> The closest I got was to use :process-command-line nil, in which case
> what you get in *command-line-strings* is the command line used to
> create the executable, but then, I don't see a way to retrieve the one
> used to launch the executable. Is it possible to get it somehow ?
I think the answer to that is to replace EXT::PROCESS-COMMAND-STRINGS
with an appropriate function of your own.  Or, if :process-command-line
is nil, you can just look at lisp::lisp-command-line-list which is
basically argv as a list of strings.


More information about the cmucl-help mailing list