Hi,
Thanks to you and Mark for your answers, because I dont know that adsf exists. This is what I'm looking for.
I've tried to increasing the JVM memory but then I always obtain some memory problems (stack overflow). I supposed that this problem is because this lisp project try to load a lot of lisp files from some folders and abcl needs to compile a lot of files. The only way to compile the project was using Allegro CL or CLISP. With Allegro CL I use jlinker but there are little documentation and with CLISP I use Jacol but the same problem.
No problem with the machine compiled files, because I'll run always with abcl and Windows.
I'll try to compile all files and package with adsf and then try to load some .fasl into java with abcl and trying to load some lisp functions into java swing.
Thanks
-----Mensaje original----- De: Alessio Stalla [mailto:alessiostalla@gmail.com] Enviado el: miércoles, 29 de febrero de 2012 12:18 Para: santi CC: armedbear-devel@common-lisp.net Asunto: Re: [armedbear-devel] compiling lisp files outside Java and calling it after with abcl
On Wed, Feb 29, 2012 at 10:42 AM, santi scarbonell@ono.com wrote:
Hi,
Thanks for your help.
Because I've a lot of problems of java memory and Truncated class files,
my
intention is try to compile in the same platform with ABCL, but only compile, not to load from ABCL a file and then compile all files. If there are some way to compile all files with abcl and package... (I don't know
if
exists).
First, if you have memory issues, you should try increasing the maximum heap size of your JVM. The 64M default is increasingly limiting for Java applications, and while Lisp apps tend to waste less memory than Java apps with tons of frameworks, I myself raised the heap size to 256M just to be sure.
That said, you can compile and not load the files on abcl. It depends on what you're using to compile/load, with asdf it's a matter of using 'compile-op rather than 'load-op. But, the files you'll obtain will only be loadable by abcl anyway, as Mark explains in his post on the abcl blog. Still, splitting the compilation and the loading in two different sessions might help with memory issues if you really can't give more memory to the JVM.
Alessio