3 ms·
Many Lisps make it a single executable file. Can you deal with that?
by lispm 17y ago
Many Lisps make it a single executable file. Can you deal with that?
- viraptor 17y agoMe? Sure. Users? Does it create an installer, uninstaller, set of icons, executable with no manual dependencies? Besides - that's not the real problem here. It's always "possible" to do something. But if a random developer gets to write some software and still doesn't know that he can package it into a single executable... maybe there's something wrong on a different level (accessible documentation?)
- lispm 17y agoMaybe he should read the documentation that is there in the first place. What kind of installer do you need for a single executable file?
- Xurinos 17y agoRegistry entries (for Windows deploys), data files, silly DRM stuff, etc. You'd want an installer/uninstaller for your more complex deployments. But that's not something one should reasonably expect from a Lisp REPL or compiler; that's just packaging, and there are installers out there that excel at that. I suppose it would be expected that modern Lisp IDEs have support for that.
- lispm 17y agoLispWorks for example is installed with one of the usual installers. Including documentation, icons, data files, etc. On the Mac I would use LispWorks to create the usual application directory that can be dragged into the systems' application folder - the usual and easiest way to install applications on the Mac. LispWorks has a delivery guide that explains how to deliver applications on Unix, Windows, Linux, FreeBSD and Mac OS X. http://www.lispworks.com/documentation/lw60/DV/html/delivery.htm http://www.lispworks.com/documentation/lw60/DV/html/delivery...