Re: windows build

[Reini U. <rei...@gm...>]

Reini Urban
ru...@cp...



> On Mar 19, 2017, at 11:43 AM, Bruno Haible <br...@cl...> wrote:
> 
> Hi Reini,
> 
>> 3. I’m in the progress to add continuous integration via travis (linux, OS X) and appveyor (Windows).
>> ...
>> https://github.com/rurban/clisp/commit/7b64a9b41d74460dc361e117700eee9713601ea0
> 
> Can you make the builds work on a machine that has not only MSVC but also
> Cygwin installed?

Cygwin would be nice, esp. to produce releases, but I’m not sure if Appveyor provides such an
image yet. They are just a small Russian company, not so high-powered as Travis in Berlin.

First I wanted to get MSVC passing, then I wanted to switch over to mingw, which is supported,
and smoke with win32 and win64.

Eventually add a cygwin setup in a local cache, for much easier testing, but I haven’t done
this yet in other projects. I have to look around.
I gave up on cygwin locally some years ago, as I could switch fully to darwin/linux and do
not maintain my windows machines anymore.
Only eventually I’ll have to do that, most likely to debug libsigsegv on win64. This was the
latest blocker when I left.

> I'm asking because nowadays my preferred way to produce native Windows binaries
> is by using Cygwin as a development environment, see [1], as it
>  - does not require to manually maintain a config.h (since it's fully
>    autoconfiguring),
>  - does not require the complexity in makemake.in regarding backslashes vs.
>    slashes (since the build relies on GNU make, not nmake),
>  - does not require to regularly update win32msvc/makefile.msvc* (the last
>    update was in 2010!)

Yes. I explicitly wanted to catch some errors there, on such old platforms.
Apparently I found some :)

> In other words, is much much simpler. But it requires Cygwin tools. Or in the
> future, the Microsoft WSL [2] may be reliable enough for this task as well.
> 
> Bruno
> 
> [1] http://git.savannah.gnu.org/gitweb/?p=libsigsegv.git;a=blob;f=README.windows
> [2] https://msdn.microsoft.com/en-us/commandline/wsl/about
>