Raymond Toy wrote: >From looking at the save-lisp in save.lisp, the command line is >processed after all of the *after-save-initializations* have been >run. I suppose it's possible to reverse this order, but I don't know >what impact that has. Perhaps you can do a save-lisp with >:process-command-line nil, and have an *after-save-initializations* >function that is run early enough to call >(ext:process-command-strings). > > A quick test seems to confirm that this works, too.
>Also, perhaps looking at lisp::*cmucl-core-path* might help. [...] > > lisp::*cmucl-core-path* was exactly what I needed. I think it's the least invasive solution. Thanks a lot, Andreas
