From: Peter G. <pe...@ar...> - 2005-05-31 18:42:29
|
The first official release of Armed Bear Common Lisp as an independent entity (i.e. independent of j) is now available: http://armedbear.org/abcl-0.0.5.tar.gz http://armedbear.org/abcl-0.0.5.zip This is a source release only, and I'm just announcing it here (and maybe on #lisp). The main purpose of this release is to identify build and packaging issues. There's a lot of administrivia involved in setting up ABCL as an independent project. This is just the first step in that direction. There's a whole new build system in this release. J used two different build systems, one based on configure and make and the other on Ant. The configure/make system was awkward to use on Windows, since it required Cygwin, and the Ant-based system was, well, based on Ant. ABCL now has an entirely Lisp-based build system. It works (modulo bugs) with SBCL, CMUCL, Allegro, LispWorks, and ABCL itself. And it works on both Linux and Windows. (I see no reason why it would fail on OS X, but I don't have a Mac to test on.) It's really very simple to use. First, you edit the file customizations.lisp, in the root directory of the source distribution, to suit your situation. The only thing you really MUST do is make sure that *JDK* gets set to the root directory of the JDK you want to use for the build. If you unset everything else, the build system will use the relevant components from the JDK you've selected. The file customizations.lisp is just a normal Lisp source file that gets loaded by INITIALIZE-BUILD, so it can contain arbitrary Lisp code. Then you fire up one of the aforementioned Lisps in the root directory of the source distribution, and do (load "build-abcl.lisp") followed by (build-abcl:build-abcl :full t) And that's it. The build generates a shell script called "abcl" (or, on Windows, a batch file called "abcl.bat") that you can use to start ABCL. If you get a chance to try this out, please let me know if you run into any problems. There are a lot of operating systems, versions of Java, and host Lisps, and I've only tried a few combinations myself, so I'm sure there will be problems. I'd even like to hear from you if things go well. And patches that make things work, of course, are always wonderful. For the record, ABCL 0.0.5 fails 79 out of 20817 test in the GCL ANSI test suite. And ABCL's CLOS is still buggy, incomplete, and slow. Thanks for your support. -Peter |
From: Andras S. <as...@ma...> - 2005-06-01 07:57:36
|
On Tue, 31 May 2005, Peter Graves wrote: > The first official release of Armed Bear Common Lisp as an independent > entity (i.e. independent of j) is now available: Great news! > If you get a chance to try this out, please let me know if you run into > any problems. There are a lot of operating systems, versions of Java, > and host Lisps, and I've only tried a few combinations myself, so I'm > sure there will be problems. I'd even like to hear from you if things > go well. And patches that make things work, of course, are always > wonderful. No problems on Linux with Sun's JDK 1.5.0 and ABCL, ACL and LW. > > For the record, ABCL 0.0.5 fails 79 out of 20817 test in the GCL ANSI > test suite. And ABCL's CLOS is still buggy, incomplete, and slow. Very impressive, especially now that Paul Dietz declared the test suite "close to done"! Andras |
From: Peter G. <pe...@ar...> - 2005-06-01 14:39:43
|
On Wed, 1 Jun 2005 at 09:57:19 +0200, Andras Simon wrote: > No problems on Linux with Sun's JDK 1.5.0 and ABCL, ACL and LW. Great! Thanks for the report! -Peter |
From: glr <gl...@rc...> - 2005-06-01 11:29:03
|
Peter ... Are there any differences between this and the lisp portion of the J CVS tree? gregory On Tue, 31 May 2005 11:42:20 -0700, Peter Graves <pe...@ar...> wrote: > The first official release of Armed Bear Common Lisp as an independent > entity (i.e. independent of j) is now available: > > http://armedbear.org/abcl-0.0.5.tar.gz > http://armedbear.org/abcl-0.0.5.zip > > This is a source release only, and I'm just announcing it here (and > maybe on #lisp). > > The main purpose of this release is to identify build and packaging > issues. > > There's a lot of administrivia involved in setting up ABCL as an > independent project. This is just the first step in that direction. > > There's a whole new build system in this release. > > J used two different build systems, one based on configure and make and > the other on Ant. The configure/make system was awkward to use on > Windows, since it required Cygwin, and the Ant-based system was, well, > based on Ant. > > ABCL now has an entirely Lisp-based build system. It works (modulo > bugs) with SBCL, CMUCL, Allegro, LispWorks, and ABCL itself. And it > works on both Linux and Windows. (I see no reason why it would fail > on OS X, but I don't have a Mac to test on.) > > It's really very simple to use. > > First, you edit the file customizations.lisp, in the root directory of > the source distribution, to suit your situation. > > The only thing you really MUST do is make sure that *JDK* gets set to > the root directory of the JDK you want to use for the build. If you > unset everything else, the build system will use the relevant > components from the JDK you've selected. The file customizations.lisp > is just a normal Lisp source file that gets loaded by INITIALIZE-BUILD, > so it can contain arbitrary Lisp code. > > Then you fire up one of the aforementioned Lisps in the root directory > of the source distribution, and do > > (load "build-abcl.lisp") > > followed by > > (build-abcl:build-abcl :full t) > > And that's it. > > The build generates a shell script called "abcl" (or, on Windows, a > batch file called "abcl.bat") that you can use to start ABCL. > > If you get a chance to try this out, please let me know if you run into > any problems. There are a lot of operating systems, versions of Java, > and host Lisps, and I've only tried a few combinations myself, so I'm > sure there will be problems. I'd even like to hear from you if things > go well. And patches that make things work, of course, are always > wonderful. > > For the record, ABCL 0.0.5 fails 79 out of 20817 test in the GCL ANSI > test suite. And ABCL's CLOS is still buggy, incomplete, and slow. > > Thanks for your support. > > -Peter > > > > ------------------------------------------------------- > This SF.Net email is sponsored by Yahoo. > Introducing Yahoo! Search Developer Network - Create apps using Yahoo! > Search APIs Find out how you can build Yahoo! directly into your own > Applications - visit > http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 > _______________________________________________ > armedbear-j-devel mailing list > arm...@li... > https://lists.sourceforge.net/lists/listinfo/armedbear-j-devel -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ |
From: Peter G. <pe...@ar...> - 2005-06-01 14:10:10
|
On Wed, 01 Jun 2005 at 06:26:34 -0700, glr wrote: > Are there any differences between this and the lisp portion of the J > CVS tree? When ABCL 0.0.5 was released, there were no differences at all in the code. The new build system pulls the files for the ABCL distribution right out of the j source tree. Since 0.0.5 was released, I've fixed a bug and done a few CVS commits, so the j tree has started to diverge from the 0.0.5 release. In addition, the j tree still contains support for the old build systems. At some point, ABCL will get its own source repository, but that's still a bit down the road. -Peter |