Since it's rapidly becoming an FAQ
... additional magic in asdf-module.mk to make synthetic fasls
allowing REQUIRE on an asdf module to work without
a loaded ASDF.
... does not work for the ASDF-INSTALL contrib, because REQUIRE
goes for the file named "asdf-install" rather than
"asdf-install.fasl" in preference. Probably want to fix
REQUIRE for that, but that's pending the other REQUIRE
issues
$(SBCL) --eval '(load "../asdf/asdf")' \
--eval "(setf asdf::*central-registry* '((MERGE-PATHNAMES \"systems/\" (TRUENAME (SB-EXT:POSIX-GETENV \"SBCL_HOME\")))))" \
--eval "(asdf:operate 'asdf:load-op :$(SYSTEM))" \
+ --eval "(progn (when (probe-file \"$(SYSTEM).fasl\") (error \"fasl file exists\")) (with-open-file (s \"$(SYSTEM).lisp\" :direction :output :if-exists :error) (print (quote (require :asdf)) s) (print (quote (require :$(SYSTEM))) s)) (compile-file \"$(SYSTEM).lisp\") (delete-file \"$(SYSTEM).lisp\"))" \
--eval "(quit)"
test: all
;;; checkins which aren't released. (And occasionally for internal
;;; versions, especially for internal versions off the main CVS
;;; branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".)
-"0.8.4.23"
+"0.8.4.24"