[Ecls-list] standalone executable under Windows with MSVC and socket support

[Matthew Mondor]

On Tue, 12 Jun 2012 09:32:35 +0200
Antonio Bonifati <antonio.bonifati at gmail.com> wrote:

> Unfortunately, I do not have a C program, I am compiling only Lisp code.
> Anyway, I think I will distribute the three or two files (exe, ucd.dat,
> ecl.dll) in the same directory. As a matter of fact, requiring users to
> install the whole ECL distribution for Windows just to run my little
> program is overkill. These three files are much smaller than the whole
> thing.

I could be wrong, but it's possible that to observe the LGPL it also be
necessary to keep ecl.dll separate, such that users could upgrade or
recompile the LGPL parts from source and still use your application,
unless you also provide your application's source.

> :prologue-code and :epilogue-code didn't work for me here.

Those code sections are special if I remember, and I also had issues
with it (among other things signal handlers did not exist or such).

In a test standalone application I wrote, I opted to instead have code
at the first level compile conditionally on a feature.  My build
script set the feature before building the system in standalone mode
(it otherwise is considered loaded for interactive use within SLIME).
This was for unix, and ASDF wasn't used, but in case it could be
helpful, check the bottom of this file:
http://cvs.pulsar-zone.net/cgi-bin/cvsweb.cgi/mmondor/mmsoftware/cl/test/irclog.lisp?rev=1.65;content-type=text%2Fplain

Its build script was:
http://cvs.pulsar-zone.net/cgi-bin/cvsweb.cgi/mmondor/mmsoftware/cl/test/irclog-build.sh?rev=1.2;content-type=text%2Fplain
-- 
Matt