ooh - thanks :)
FWIW, I've been updating the system.lisp using jar uf as it's usually post-build that I'm doing this stuff. However, I've been prototyping a distribution system that has two parts - an abcl combined with all java libraries, and a second, smaller file with compiled lisp files as a manner of distribution and so it may be that I will suggest some generic code for system.lisp that supports that. I'll try to write it up in the next couple of weeks. I've already successfully deployed using this, but it still needs some further review and work (for instance testing and using your fix to directory/wild)
-Alan
Current status:
http://code.google.com/p/lsw2/downloads/list http://code.google.com/p/lsw2/source/browse/trunk/packit/org/armedbear/lisp/... http://code.google.com/p/lsw2/source/browse/trunk/packit/jar-current-classpa... http://code.google.com/p/lsw2/source/browse/trunk/packit/jar-current-loaded-... http://code.google.com/p/lsw2/source/browse/trunk/owl2/abcl-module-owltool.l...
On Thu, May 13, 2010 at 8:55 AM, Mark Evenson evenson@panix.com wrote:
On 5/12/10 12:09 PM, Mark Evenson wrote: […]
How can I establish that my code running as called from system.lisp runs in a normal debugging environment?
This code is executed before the standard restarts have been put into place, as far as I can tell. Perhaps this code should be executed later?
I [moved the execution of of 'system.lisp'][1] later in the boot after the condition system has been initialized so that conditions now drop to the debugger.
And [there is now a facility to customize the code in 'system.lisp'][2] as part of the Ant build: set the Ant property 'abcl.startup.file' to refer to a file whose forms will be appended.
Please let me know if this doesn't work out for you.
-- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."
armedbear-devel mailing list armedbear-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel