ArmedBear / J

(message (Hello 'Peter)
(you :wrote  :on '(Tue, 31 May 2005 11:42:20 -0700))
(

 PG> J used two different build systems, one based on configure and make and
 PG> the other on Ant. The configure/make system was awkward to use on
 PG> Windows, since it required Cygwin,

it can be used with MSYS, the part of MinGW. its distributive is only 3
megs, it just works, and would be useful on windows machine anyway. so i
quite enjoyed building abcl

 PG> ABCL now has an entirely Lisp-based build system. It works (modulo
 PG> bugs) with SBCL, CMUCL, Allegro, LispWorks, and ABCL itself. And it
 PG> works on both Linux and Windows.

there are no SBCL and CMUCL under Windows.
allegro and lispworks are commercial products, installing their trial
versions to just to build abcl ..is somewhat unpleasant :)
it refuses to work with old version of ABCL -- javac tells something about
wrong options..

so, as for me, J's build system was somewhat more comfortable.. if this
lisp-based build system was working with clisp at least..

)
(With-best-regards '(Alex Mizrahi) :aka 'killer_storm)
"People who lust for the Feel of keys on their fingertips (c) Inity")

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

On Tue, 31 May 2005, Alex Mizrahi wrote:

> so, as for me, J's build system was somewhat more comfortable.. if this
> lisp-based build system was working with clisp at least..

I think you could easily make it work with clisp.

Andras

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 <peter@...>  
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
> armedbear-j-devel@...
> https://lists.sourceforge.net/lists/listinfo/armedbear-j-devel



-- 
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

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

On Tue, 31 May 2005 at 22:51:12 +0300, Alex Mizrahi wrote:
> it can be used with MSYS, the part of MinGW. its distributive is only
> 3 megs, it just works, and would be useful on windows machine anyway.
> so i quite enjoyed building abcl

Yeah. I don't think Cygwin is bad, either, myself, but I'd like to move
away from requiring unrelated external packages to build ABCL.

This transition will be a bit awkward at the beginning.

In the near future, ABCL releases will include a binary distribution as
well as a source distribution, and you'll be able to use ABCL from the
binary distribution to build a new ABCL from the source distribution,
so I think the awkwardness will go away eventually.

> there are no SBCL and CMUCL under Windows.
> allegro and lispworks are commercial products, installing their trial
> versions to just to build abcl ..is somewhat unpleasant :)

Windows is somewhat unpleasant to begin with... :)

> it refuses to work with old version of ABCL -- javac tells something
> about wrong options..

That sounds like a bug. I'll try to make sure that ABCL 0.0.7 can be
built with ABCL 0.0.6 on all platforms.

> so, as for me, J's build system was somewhat more comfortable.. if
> this lisp-based build system was working with clisp at least..

For the time being, you can still get the source from j's CVS and use
either of the old build systems; I haven't ripped them out and don't
plan to do so anytime soon.

I actually spent a long time trying to get the new build system to work
with clisp, but ran into too many problems and gave up at the last
minute. (I really wanted to get 0.0.5 out the door before going on
vacation today, and I was running out of time.) I'll try again for
0.0.6.

Thanks for your comments!

-Peter

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

(message (Hello 'Peter)
(you :wrote  :on '(Wed, 1 Jun 2005 07:37:49 -0700))
(

 ??>> there are no SBCL and CMUCL under Windows.
 ??>> allegro and lispworks are commercial products, installing their trial
 ??>> versions to just to build abcl ..is somewhat unpleasant :)

 PG> Windows is somewhat unpleasant to begin with... :)

with Solaris situation is even worse, i think..

by the way, i found ABCL 0.0.5 works with slime-for-emacs back again, at
least i haven't seen that nasty crashes. it doesn't work as is because of
changes in CLOS internals, but after commenting some stuff it somewhat
works.. 8]

if it really works it is really good, i'll try to use it for my servlet
stuff instead of old version -- maybe changes in internal structure healed
problems with slow speed when working in servlet..

)
(With-best-regards '(Alex Mizrahi) :aka 'killer_storm)
"People who lust for the Feel of keys on their fingertips (c) Inity")