| 1 | ASDF-JAR |
|---|
| 2 | ======== |
|---|
| 3 | |
|---|
| 4 | Mark Evenson |
|---|
| 5 | Created: 20-JUN-2011 |
|---|
| 6 | Modified: 20-JUN-2011 |
|---|
| 7 | |
|---|
| 8 | ASDF-JAR provides a system for packaging ASDF systems into jar |
|---|
| 9 | archives for ABCL. Given a running ABCL image with loadable ASDF |
|---|
| 10 | systems the code in this package will recursively package all the |
|---|
| 11 | required source and fasls in a jar archive . |
|---|
| 12 | |
|---|
| 13 | To install ASDF systems, [Quicklisp]() is probably the best |
|---|
| 14 | contemporary solution, although a version of ASDF-INSTALL is also |
|---|
| 15 | packaged in ABCL contribs. |
|---|
| 16 | |
|---|
| 17 | [Quicklisp]: http://www.quicklisp.org |
|---|
| 18 | |
|---|
| 19 | Once the requisite ASDF systems have been installed, ensure that this |
|---|
| 20 | contrib is loaded via |
|---|
| 21 | |
|---|
| 22 | CL-USER) (require :abcl-contrib) |
|---|
| 23 | CL-USER> (require :asdf-jar) |
|---|
| 24 | |
|---|
| 25 | Then, to say package the Perl regular expression system ("CL-PPCRE"), |
|---|
| 26 | one uses the ASDF-JAR:PACKAGE as follows: |
|---|
| 27 | |
|---|
| 28 | CL-USER> (asdf-jar:package :cl-ppcre) |
|---|
| 29 | ; Loading #P"/home/evenson/quicklisp/dists/quicklisp/software/cl-ppcre-2.0.3/cl-ppcre.asd" ... |
|---|
| 30 | ; Loaded #P"/home/evenson/quicklisp/dists/quicklisp/software/cl-ppcre-2.0.3/cl-ppcre.asd" (0.029 seconds) |
|---|
| 31 | Packaging ASDF definition of #<ASDF:SYSTEM "cl-ppcre"> |
|---|
| 32 | as /var/tmp/cl-ppcre-all-2.0.3.jar. |
|---|
| 33 | Packaging contents in /var/tmp/cl-ppcre-all-2.0.3.jar |
|---|
| 34 | with recursive dependencies. |
|---|
| 35 | #P"/var/tmp/cl-ppcre-all-2.0.3.jar" |
|---|
| 36 | |
|---|
| 37 | The resulting jar contains all source and fasls required to run the |
|---|
| 38 | ASDF system including any transitive ASDF dependencies. Each asdf |
|---|
| 39 | system is packaged under its own top level directory within the jar |
|---|
| 40 | archive. The jar archive itself is numbered with the version of the |
|---|
| 41 | system that was specified in the packaging. |
|---|
| 42 | |
|---|
| 43 | To load the system from the jar one needs to add the ASDF file |
|---|
| 44 | locations to the ASDF *CENTRAL-REGISTRY*. If one wishes to load the |
|---|
| 45 | fasls from the jar alone, one needs to tell ASDF not to override its |
|---|
| 46 | output translation rules. The function ASDF-JAR:ADD-TO-JAR does both |
|---|
| 47 | of these options serving as the basis for customized load strategies |
|---|
| 48 | tailored to end-user deployment needs. So, after |
|---|
| 49 | |
|---|
| 50 | CL-USER> (asdf-jar:add-to-asdf "/var/tmp/cl-ppcre-all-2.0.3.jar") |
|---|
| 51 | |
|---|
| 52 | a subsequent |
|---|
| 53 | |
|---|
| 54 | CL-USER> (asdf:load-system :cl-ppcre) |
|---|
| 55 | |
|---|
| 56 | should load the ASDF system from the jar. |
|---|
| 57 | |
|---|
| 58 | Setting CL:*LOAD-VERBOSE* will allow one to verify that the subsequent |
|---|
| 59 | load is indeed coming from the jar. |
|---|
