[armedbear-devel] Deploying compiled ABCL apps/elements

Matt Lamari matt.lamari at gmail.com
Tue Jul 21 18:46:58 UTC 2009


What's the planned endgame for the system?  Is saved-memory-image
remotely feasible?  Or a jar with coded that would create the image?  Or
something else?


Alessio Stalla wrote:
> ABCL currently can not save a memory image, so you're stuck with
> loading compiled files (perhaps with asdf or similar, if it accepts
> the absence of source files). ABCL has the capability to load files
> from a jar archive, but I think it's internal machinery and not
> exposed through a public API, though I might be wrong on this point.
> However, loading files from a jar probably forces you to drop asdf and
> any other system definition facility and manually load files in the
> correct order.
>
> hth,
> Alessio
>
> On Tue, Jul 21, 2009 at 2:52 PM, Matt Lamari<matt.lamari at gmail.com> wrote:
>   
>> What is the mechanism for converting source code or an in-memory image
>> (or fragment thereof) into a deployable unit?  Just point me at a
>> function name/document and I can take it from there. . . .
>>
>> Thanks,
>> Matt
>>
>>
>>
>> _______________________________________________
>> armedbear-devel mailing list
>> armedbear-devel at common-lisp.net
>> http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel
>>
>>     





More information about the armedbear-devel mailing list