[movitz-devel] Re: building image

Vikas N Kumar vikasnkumar at users.sourceforge.net
Mon Oct 23 13:28:57 UTC 2006

Thanks Frode.
But am I doing the right thing by ignoring the errors that are
occuring while compiling los0-gc.lisp ?


On 23 Oct 2006 08:37:44 +0200, Frode Vatvedt Fjeld
<ffjeld at common-lisp.net> wrote:
> Hi Vikas,
> "Vikas N Kumar" <vikasnkumar at users.sourceforge.net> writes:
> > How does one create the final .img file ?
> Use the function dump-image, which takes as arguments the pathname of
> the image file (default "los0-image"), and the (symbolic) image you
> want to dump, which is typically the thingy that was just returned
> from create-image.
> Create-image will by default set the variable movitz:*image* to the
> same value as it returns. Many movitz functions subsequently use this
> variable as the (default) image to manipulate, including dump-image.
> There are functions that do useful manipulations of an existing
> image. Most notable of these is movitz-compile-file, which compiles
> the contents of a file pretty much the way you expect. That is, if the
> file contains "(defun foo (x) (1+ x))", then the current *image*'s
> function definition for foo will be updated to reflect this. Then,
> the next image generated by dump-image will contain the new foo.
> The typical task, then, of the Movitz "IDE" (in whatever form, there
> are I believe two variants of Emacs integration in CVS) is to have a
> keybinding M-C-x or C-c C-c that places the current top-level form in
> a temporary file and applies movitz-compile-file to that file.
> Regards,
> --
> Frode Vatvedt Fjeld
> _______________________________________________
> movitz-devel site list
> movitz-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/movitz-devel


More information about the movitz-devel mailing list