[armedbear-devel] [PATCH] build-from-lisp.sh
![](https://secure.gravatar.com/avatar/e30bc676ee7d74ff2b67b431353a8ab8.jpg?s=120&d=mm&r=g)
The following makes it possible to build ABCL from the command line directly: ./build-from-lisp.sh sbcl ./build-from-lisp.sh clisp etc. -T. -- Diese Nachricht wurde auf Viren und andere gefaerliche Inhalte untersucht und ist - aktuelle Virenscanner vorausgesetzt - sauber. Freebits E-Mail Virus Scanner
![](https://secure.gravatar.com/avatar/b053ca7abf2716d9df3ce01278d60947.jpg?s=120&d=mm&r=g)
Tobias C. Rittweiler wrote:
The following makes it possible to build ABCL from the command line directly:
./build-from-lisp.sh sbcl
./build-from-lisp.sh clisp
I think you missed your patching of "build-abcl.lisp" with a top-level call to BUILD-ABCL (which you mention in your patch of README) right? I'm a little reluctant to patch 'build-abcl.lisp' in this way, as it mutates the behavior of the "BUILD-ABCL" ASDF definition contained in "abcl.asd" to always begin executing the build process at 'ASDF:LOAD-OP time. Couldn't we either a) evaluate a (BUILD-ABCL) form after the load or b) create another Lisp file (like "do-build-abcl.lisp") that loads "build-abcl.lisp" and then evaluates the top-level load? -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."
![](https://secure.gravatar.com/avatar/29e40ec843bec4b66414022ddce75718.jpg?s=120&d=mm&r=g)
On Mon, Jul 13, 2009 at 10:31 AM, Mark Evenson<evenson@panix.com> wrote:
Tobias C. Rittweiler wrote:
The following makes it possible to build ABCL from the command line directly:
./build-from-lisp.sh sbcl
./build-from-lisp.sh clisp
I think you missed your patching of "build-abcl.lisp" with a top-level call to BUILD-ABCL (which you mention in your patch of README) right?
I'm a little reluctant to patch 'build-abcl.lisp' in this way, as it mutates the behavior of the "BUILD-ABCL" ASDF definition contained in "abcl.asd" to always begin executing the build process at 'ASDF:LOAD-OP time. Couldn't we either a) evaluate a (BUILD-ABCL) form after the load or b) create another Lisp file (like "do-build-abcl.lisp") that loads "build-abcl.lisp" and then evaluates the top-level load?
It's possible to give 2 options to ABCL at the command line: --load <some file> --eval "<some form>" Although I didn't look at the patch, I guess this is what you're after? Bye, Erik.
![](https://secure.gravatar.com/avatar/b053ca7abf2716d9df3ce01278d60947.jpg?s=120&d=mm&r=g)
Erik Huelsmann wrote: […]
I'm a little reluctant to patch 'build-abcl.lisp' in this way, as it mutates the behavior of the "BUILD-ABCL" ASDF definition contained in "abcl.asd" to always begin executing the build process at 'ASDF:LOAD-OP time. Couldn't we either a) evaluate a (BUILD-ABCL) form after the load or b) create another Lisp file (like "do-build-abcl.lisp") that loads "build-abcl.lisp" and then evaluates the top-level load?
It's possible to give 2 options to ABCL at the command line:
--load <some file> --eval "<some form>"
Although I didn't look at the patch, I guess this is what you're after?
Right, but its a little more involved, as one has to have the correct syntax for every Lisp that the shell scripts wishes to invoke, which takes some hunting around. I don't have access to all the Lisp implementations that Tobias has put in here. -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."
participants (3)
-
Erik Huelsmann
-
Mark Evenson
-
Tobias C. Rittweiler