Reason for no release in 8 years - maybe building a Windows installer?

Wolfgang Dautermann <[email protected]> Mon, 7 Jan 2019 08:33:03 +0100
Newsgroups gmane.lisp.clisp.devel
Message-ID <[email protected]>
Dear Clisp-Team,

I think, I wrote about that some years ago, Clisp is used for the
Windows installer for the CAS "Maxima" - I create the installers using
crosscompiliation (and since there are no crosscompilers for Lisp, I run
the Windows version on Linux using 'wine'). That works good, but often I
get asked, why I use a 8 year old release - well, because there is no
newer one.

Whats the reason for that? CLISP is actively developed, there were even
GSOC projects for CLISP. And I assume, the current git version is *much*
better than a release which is more than 8 years old.

Is the problem creating a Windows installer? I tried to create one -
again by crosscompiling - and it worked for the core system. ("make
boot" instead of "make base"). I you want to try it, you can find the
code and a readme here:

https://wolfgang.dautermann.at/clisp-crosscompile.tar.gz
https://wolfgang.dautermann.at/clisp-crosscompile-readme.txt

On a Ubuntu system (I used 16.04) install crosscompilers and necessary
programs:
apt-get install gcc-mingw-w64-i686 mingw-w64-i686-dev nsis wine cmake
(you will also need native compilers and libsigsegv and libffcall as for
a native Clisp build).
Extract the tar.gz and change into the 'build' directory. There do:
cmake ..
make
make package

This will download clisp (git), libsigsegv and libffcall, crosscompile
the programs (clisp twice, first native and then for Windows) and build
a Windows installer.

I one tries to build a complete version (e.g. by using "cmake
-DCLISP_STAGE=base ..", see the readme), the compilation process stops
at some point with the message
checking for CLISP version... configure: error:
'/home/dauti/Software/clisp/build/clisp/clisp-prefix/src/clisp-build/clisp'
is not a CLISP

But the mentioned program works - here it is a shell script which calls
the crosscompiled clisp.exe using wine. Maybe there is somewhere a check
which checks the type of the program and expects a Windows binary, I
have not found it. Perhaps someone of you knows the solution?


If you have questions, or something does not work for you, just ask me.
If you want to include the code into Clisp, feel free to do so. If so,
maybe I should polish and document it better.

Best regards, Wolfgang




_______________________________________________
clisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel