1 | GENERAL INFORMATION |
---|
2 | =================== |
---|
3 | |
---|
4 | Armed Bear Common Lisp is an implementation of ANSI Common Lisp that |
---|
5 | runs in a Java virtual machine. |
---|
6 | |
---|
7 | |
---|
8 | LICENSE |
---|
9 | ======= |
---|
10 | |
---|
11 | Armed Bear Common Lisp is distributed under the GNU General Public |
---|
12 | License (with a special exception described below). |
---|
13 | |
---|
14 | A copy of GNU General Public License (GPL) is included in this |
---|
15 | distribution, in the file COPYING. |
---|
16 | |
---|
17 | Linking this software statically or dynamically with other modules is |
---|
18 | making a combined work based on this software. Thus, the terms and |
---|
19 | conditions of the GNU General Public License cover the whole |
---|
20 | combination. |
---|
21 | |
---|
22 | As a special exception, the copyright holders of this software give |
---|
23 | you permission to link this software with independent modules to |
---|
24 | produce an executable, regardless of the license terms of these |
---|
25 | independent modules, and to copy and distribute the resulting |
---|
26 | executable under terms of your choice, provided that you also meet, |
---|
27 | for each linked independent module, the terms and conditions of the |
---|
28 | license of that module. An independent module is a module which is not |
---|
29 | derived from or based on this software. If you modify this software, |
---|
30 | you may extend this exception to your version of the software, but you |
---|
31 | are not obligated to do so. If you do not wish to do so, delete this |
---|
32 | exception statement from your version. |
---|
33 | |
---|
34 | |
---|
35 | BUILDING |
---|
36 | ======== |
---|
37 | |
---|
38 | To build ABCL, you'll need |
---|
39 | |
---|
40 | 1) a 1.5 JDK, |
---|
41 | |
---|
42 | and either |
---|
43 | |
---|
44 | 2.1) a supported Common Lisp implementation (SBCL, CMUCL, OpenMCL, |
---|
45 | Allegro, LispWorks, or CLISP) |
---|
46 | |
---|
47 | or |
---|
48 | |
---|
49 | 2.2) a version of Apache Ant (post 1.7.1) |
---|
50 | |
---|
51 | |
---|
52 | Lisp-based |
---|
53 | ---------- |
---|
54 | |
---|
55 | Copy the file 'customizations.lisp.in' to customization.lisp', in the |
---|
56 | directory containing this README file, editing to suit your situation, |
---|
57 | paying attention to the comments in the file. |
---|
58 | |
---|
59 | Start up one of the supported Common Lisp implementations in the |
---|
60 | directory containing this README file. |
---|
61 | |
---|
62 | Load build-abcl.lisp: |
---|
63 | |
---|
64 | (load "build-abcl.lisp") |
---|
65 | |
---|
66 | Then do: |
---|
67 | |
---|
68 | (build-abcl:build-abcl :clean t :full t) |
---|
69 | |
---|
70 | Wait for the build to finish and exit the host Lisp. |
---|
71 | |
---|
72 | Use abcl.bat on Windows or ./abcl on Unix to start ABCL. (Note that |
---|
73 | abcl.bat and abcl contain absolute paths, so you'll need to edit the |
---|
74 | relevant file if you move things around after the build.) |
---|
75 | |
---|
76 | If the build fails in the javac stage, you might have better luck with |
---|
77 | this: |
---|
78 | |
---|
79 | (build-abcl:build-abcl :clean t :full t :batch nil) |
---|
80 | |
---|
81 | This invokes javac separately for each .java file, which is |
---|
82 | considerably slower but avoids running into limitations on command |
---|
83 | line length. |
---|
84 | |
---|
85 | Ant-based |
---|
86 | --------- |
---|
87 | |
---|
88 | With ant-1.7.1 in your path executing |
---|
89 | |
---|
90 | ant -find build.xml abcl.wrapper |
---|
91 | |
---|
92 | from the directory containing this README file will create an |
---|
93 | executable wrapper ('abcl' under UNIX, 'abcl.bat' under Windows) which |
---|
94 | can use to run ABCL. |
---|
95 | |
---|
96 | |
---|
97 | BUGS |
---|
98 | ==== |
---|
99 | |
---|
100 | ABCL is a very young implementation. You are certain to encounter |
---|
101 | bugs. |
---|
102 | |
---|
103 | ABCL 0.0.9 fails 54 out of 21344 tests in the GCL ANSI test suite. |
---|
104 | |
---|
105 | ABCL's CLOS does not handle on-the-fly redefinition of classes |
---|
106 | correctly, and in any event is intolerably slow. There is no support |
---|
107 | for the long form of DEFINE-METHOD-COMBINATION, and certain other |
---|
108 | required CLOS features are also missing. Enough CLOS is there to run |
---|
109 | ASDF and CL-PPCRE, if you're in no hurry. |
---|
110 | |
---|
111 | There is no MOP worth mentioning. |
---|
112 | |
---|
113 | Since this is a very early public release, there might be build |
---|
114 | problems as well as runtime bugs. |
---|
115 | |
---|
116 | Please report problems to the j-devel mailing list: |
---|
117 | |
---|
118 | armedbear-j-devel@lists.sourceforge.net |
---|
119 | |
---|
120 | Have fun! |
---|
121 | |
---|
122 | Peter Graves |
---|
123 | October 18, 2005 |
---|