On Dec 16, 2005, at 4:36 AM, [EMAIL PROTECTED] wrote: > Whilst I'm not currently involved in any development on Lisp > compilers, > I know at least one person on this list is... realistically, how > difficult > would it be to ship (say) SBCL as a 'libsbcl.so' + a couple of > binaries > that get the environment (listener) up when invoked? (This is one > of the > things I think Dylan got right; everything is built as a shared > library. > whether this is possible in Lisp I'm not sure (but can't see why > not)). > > Maybe I'm just showing my newbie colours here though ;-)
Is there any particular requirement for this to be an ELF (or your platform's native) shared object? Generally speaking C object file formats weren't made for Lisp. Most binary software I download for Linux comes in a directory which includes a number of different pieces, including shared objects, binaries, data files, etc. The obvious extrapolation is that an SBCL program would be distributed as SBCL runtime + core file + data files as necessary. If I were shipping a commercial application using SBCL this is the way I would do it. Open Source projects don't seem to produce binaries naturally, though - even getting binaries up every month for SBCL is difficult, and as a compiler which depends on having a CL compiler to compile itself it's sort of difficult *not* to ship binaries at least every once in a while. Other projects don't seem to produce binaries until they get really big and complicated, or start to market themselves as turnkey apps (like Mozilla). -- Brian Mastenbrook [EMAIL PROTECTED] http://brian.mastenbrook.net/ _______________________________________________ Gardeners mailing list [email protected] http://www.lispniks.com/mailman/listinfo/gardeners
