Re: Delivering Lisp applications [was: Re: [email protected]]

--===============1371934091==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="=-likAimcG1fCjHq13W187"


--=-likAimcG1fCjHq13W187
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Wed, 2003-12-03 at 13:11, Paolo Amoroso wrote:
> I would like to start a discussion about all issues related to Lisp
> application delivery. Topics of interest include, but are not limited
> to:
>=20
> - deployment to user machines (from install scripts to things like
>   vn-cCLan/asdf-install, but for "executable" applications and not
>   source code)

Towards this end, I've been looking into tagging sbcl cores onto the end
of the sbcl runtime to create standalone executables.  The resulting
files are pretty big, but they are completely independent.  The
native-compiling lisps actually have a bit of an advantage here vs.
scripting languages because it's possible to condense a bunch of
libraries into a single core.

--=20
Miles Egan <[email protected]>

--=-likAimcG1fCjHq13W187
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQA/0MCYU4Jq/wH1PVERAqCLAKCCIngcwSTBlxmJdHeUeKXnX1iE4ACgzquf
/QgszorimcD9Fy0OxsHh7wU=
=n4mU
-----END PGP SIGNATURE-----

--=-likAimcG1fCjHq13W187--


--===============1371934091==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Clump mailing list
[email protected]
http://manly.caddr.com/mailman/listinfo/clump

--===============1371934091==--