Re: CLISP on Windows

[Bruno H. <br...@cl...>]

Hi Wolfgang,

Please keep the mailing list in CC.

Wolfgang Dautermann wrote:
> I am looking forward to a new release. People (including me) are using 
> 2.49, which is 14 years old, as that was the last release.
> 
> And Clisp *is* under active development (thanks!!), so the current code 
> is probably much better than the version from 2010.
> 
> [Since 2015 I create Windows installers for the Computeralgebrasystem 
> Maxima by crosscompiling it from Linux to Windows, and Clisp was the 
> first Lisp compiler, which allowed me to do this (running Clisp using 
> 'wine' on Linux).
> But for that task I still use 2.49 from sourceforge, as this is the 
> latest Windows version. (Other Lisp compilers are supported now in my 
> Maxima Windows installer, but of course Clisp (2.49) is still used there).]

For Maxima, the version 2.49 should be entirely sufficient (on platforms
that were supported back then).

> How does one create a Windows installer? You recommend using Cygwin as 
> development environment, I tried to set up that on Github actions, but 
> it stops during the compiliation:
> 
> ./lisp.exe -marc > marc.out
> Cannot reserve address range 0x3000000-0x300ffff .
> [../src/spvw_mmap.d:342] GetLastError() = 0x1e7: Attempt to access 
> invalid address.
> 
> See
> https://github.com/daute/clisp-crossbuild/
> and
> https://github.com/daute/clisp-crossbuild/actions/runs/11520137588/job/32070748276

The situation of the Windows port is currently a mess, because it is focused
on the MSVC compiler (whereas mingw-w64 is now generally the better approach)
on old versions of that compiler, on nmake rather than GNU make, with way too
much code for cross-compiling.

This will take a while to clean up. And the NSIS-based installer for Windows
is also out-of-date; maybe people can just unpack a zip instead?

Bruno