=cffi-grovel=, and =cffi-examples=) and all their dependencies.
If you want to install only a single system and its dependencies[fn:4] you can use
the =-s= (system) option, such as:
#+begin_src shell
clpm install -s cffi
#+end_src
You can test this was successful by starting your favorite Lisp and running:
#+begin_src common-lisp
(require :asdf)
(asdf:load-system :cffi)
#+end_src
Note how you do not need to load any CLPM code inside your Lisp image in order
to load CFFI after installing it. (Assuming you have ASDF 3+ installed).
* In-depth Documentation
For more documentation on CLPM, you may find the following files useful:
+ [[file:doc/config.org][config.org]] :: Summary of all of CLPM's configuration options.
+ [[file:doc/sources.org][sources.org]] :: Summary of all supported software repositories.
+ [[file:doc/bundle.org][bundle.org]] :: Information on how to use CLPM to manage and repeatably
install dependencies for a single project.
* Footnotes
[fn:6] On Windows, CLPM will fetch over HTTPS, but it will *not* currently
validate the certificates. See [[https://gitlab.common-lisp.net/clpm/clpm/issues/1][issue#1]] for more info.
[fn:5] All files in the primary Quicklisp distribution are served over both
HTTPS and HTTP, even though the Quicklisp client cannot use HTTPS itself.
[fn:4] Really, the entire project the system belongs to will be installed, but
only the dependencies of the specified system will be installed.
[fn:3] If you know a way to statically link SBCL against libc, please let me
know!
[fn:1] See, for example: [[https://www.quicklisp.org/beta/][Quicklisp]], [[https://github.com/fukamachi/qlot/][Qlot]], and [[https://github.com/CodyReichert/qi][Qi]].
[fn:2] Using the archive library for a full Common Lisp solution is on the