Adventures in Lisp application deployment(ahefner.livejournal.com)
ahefner.livejournal.com
Adventures in Lisp application deployment
http://ahefner.livejournal.com/15783.html
3 comments
It's true that SBCL doesn't make the binary delivery process easy.
However, both Allegro CL and Lispworks put a lot of effort into it and succeed quite well. For example, Allegro CL will automatically copy all loaded shared libraries that are not from /lib or /usr/lib to the delivery directory, which nicely solves the CFFI wrapper issue.
http://www.lispworks.com/documentation/lw51/DV/html/deluser....
http://www.franz.com/support/documentation/current/doc/deliv...
However, both Allegro CL and Lispworks put a lot of effort into it and succeed quite well. For example, Allegro CL will automatically copy all loaded shared libraries that are not from /lib or /usr/lib to the delivery directory, which nicely solves the CFFI wrapper issue.
http://www.lispworks.com/documentation/lw51/DV/html/deluser....
http://www.franz.com/support/documentation/current/doc/deliv...
> renamed libmixalot-mpg123, with these changes. The 64-bit binary doesn't have any of these problems, and should Just Work, but you have to provide your own libmpg123 as before.
I don't think he can lie. That's a big but.
I don't think he can lie. That's a big but.
What?
An attempt at humor, perhaps: http://www.google.com/search?hl=en&q=mixalot+%22big+butt...
With Smalltalk, you have to strip the development and other unused stuff out of the image, which is a messy business that can lead to exceptions showing up in front of the customer if you don't do it right. Many places just leave all that stuff in the image. It's unnecessary overhead, but Moore's law and the similar increase in disk capacity has made that into a rounding error.
(This is also why debugging and development are so magical in environments like Smalltalk. It's the default case. Debugging is often so painless, people use it to document!)