Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Creating a dedicated version of core image is a good option. You may:</p> <ol> <li><p>load <code>quicklisp</code> and <code>sb-ext:save-lisp-and-die</code> in a new image. You write a shell/bat script named, say <code>qlsbcl</code>, like this:</p> <pre><code>sbcl --core &lt;my-new-image-full-path-location&gt; "$@" </code></pre></li> <li><p>grab <code>clbuild2</code> at <a href="http://gitorious.org/clbuild2" rel="noreferrer">http://gitorious.org/clbuild2</a> and run <code>clbuild lisp</code>. You'll have to symlink clbuild to a binary directory in your path and tweak some scripts a bit if your <code>quicklisp</code> is not in the common place <em>~/quicklisp</em> (<a href="https://gist.github.com/1485836" rel="noreferrer">https://gist.github.com/1485836</a>) or if you use <code>ASDF2</code> (<a href="https://gist.github.com/1621825" rel="noreferrer">https://gist.github.com/1621825</a>). By doing so, <code>clbuild</code> create a new core with <code>quicklisp</code>, <code>ASDF</code> and anything you may add in <em>conf.lisp</em>. Now the shebang may look like this:</p> <pre><code>#!/usr/bin/env sbcl --noinform --core &lt;my-clbuild-install-directory&gt;/sbcl-base.core --script </code></pre></li> </ol> <p>The advantage of <code>clbuild</code> is that you may easily create and manage core and quicklisp installation from shell for <code>sbcl</code> (by default) or any other modern CL like <code>ccl64</code> implementation. Mixing the two techniques (script and <code>clbuild</code>) will solve your problem.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload