From ... From: Erik Naggum Subject: Re: clisp: compile Lisp program to stand alone binary? Date: 1998/10/06 Message-ID: <3116663895330295@naggum.no>#1/1 X-Deja-AN: 398237450 References: <362151b1.7389655@news.newsguy.com> <3116573412536149@naggum.no> <362782a4.85456830@news.newsguy.com> mail-copies-to: never Organization: Naggum Software; +47 8800 8879; http://www.naggum.no Newsgroups: comp.lang.lisp * trashcan@david-steuber.com (David Steuber "The Interloper") | In the windows world, C or C++ can be compiled into a single | executable image. There is no need to rely on a C/C++ compiler or run | time environment to run the program. well, in that case, you can dump a Lisp world into a new image, too. the image my current client runs on Allegro CL 5.0 has pre-dumped over 300 patches and new functions and advice and such. when the application is ready to be run directly (it's loaded from a concatenated FASL file now), it'd be a piece of cake to load it before dumping yet another image. | I don't want to rely on the pre-existance of CLISP (or any other lisp) | on another machine. I also want the code to compile into machine | code, not some byte interpreted code. only Emacs Lisp and CLISP of the commonly supported Lisps produce byte code. all others produce machine code. _that_ should be the least of your worries, actually. #:Erik