Re: clisp release history

--===============5575562872779320105==
Content-Type: multipart/alternative; boundary="000000000000145f6a05af30c12b"

--000000000000145f6a05af30c12b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Current ci status (all red for years):

https://ci.appveyor.com/project/rurban/clisp/history (windows)
https://travis-ci.org/github/rurban/clisp/builds (linux, osx)



Wolfgang Dautermann <[email protected]> schrieb am So., 13. Sep. 2020,
13:16:

> Am 12.09.20 um 18:20 schrieb Pascal Bourguignon:
> > In days of git, indeed,  the notion of release may seem irrelevant.
> >
> > However, it=E2=80=99s a public relation device.
> > A release is something we write to make people aware of our product and
> > talk about it, and forget about the competition.
>
> Hi,
> yes - and often a binary (e.g. for Windows, MacOS, etc. is *really*
> helpful.
>
> It seems, that you are working with MinGW (the last commit on
> https://gitlab.com/gnu-clisp/clisp/-/commits/master
> is 'Fix a build error on mingw.', so it seems to work. (at least, a
> native build on Windows, I assume, that is not a crosscompiled build?)
>
> An installer or zip file including the compiled Windows binary would be
> really helpful (maybe one for 32 bit and one for 64 bit).
>
> I use the latest Windows release (yes, that from 2010!) for
> crosscompiling the open source CAS Maxima for Windows (using 'Wine').
>
> Now other Lisps are supported too (SBCL, ABCL), but when I started the
> idea, Clisp was the first Lisp compiler which worked. And it is still
> included.
>
> I have some code to crosscompile (using Linux as build host) Clisp (and
> the required libraries) for Windows, but it does not work now.
>
> Best regards, Wolfgang
>
>
> _______________________________________________
> clisp-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/clisp-devel
>

--000000000000145f6a05af30c12b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div dir=3D"auto">Current ci status (all red for years):<=
/div><div dir=3D"auto"><br></div><a href=3D"https://ci.appveyor.com/project=
/rurban/clisp/history">https://ci.appveyor.com/project/rurban/clisp/history=
</a> (windows)<div dir=3D"auto"><a href=3D"https://travis-ci.org/github/rur=
ban/clisp/builds">https://travis-ci.org/github/rurban/clisp/builds</a> (lin=
ux, osx)<br><div dir=3D"auto"><br><div dir=3D"auto"><br></div></div></div><=
/div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">W=
olfgang Dautermann &lt;<a href=3D"mailto:[email protected]">wolfgang@d=
autermann.at</a>&gt; schrieb am So., 13. Sep. 2020, 13:16:<br></div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">Am 12.09.20 um 18:20 schrieb Pascal Bourguignon:<br=
>
&gt; In days of git, indeed, =C2=A0the notion of release may seem irrelevan=
t.<br>
&gt; <br>
&gt; However, it=E2=80=99s a public relation device.=C2=A0<br>
&gt; A release is something we write to make people aware of our product an=
d<br>
&gt; talk about it, and forget about the competition.<br>
<br>
Hi,<br>
yes - and often a binary (e.g. for Windows, MacOS, etc. is *really* helpful=
.<br>
<br>
It seems, that you are working with MinGW (the last commit on<br>
<a href=3D"https://gitlab.com/gnu-clisp/clisp/-/commits/master" rel=3D"nore=
ferrer noreferrer" target=3D"_blank">https://gitlab.com/gnu-clisp/clisp/-/c=
ommits/master</a><br>
is &#39;Fix a build error on mingw.&#39;, so it seems to work. (at least, a=
<br>
native build on Windows, I assume, that is not a crosscompiled build?)<br>
<br>
An installer or zip file including the compiled Windows binary would be<br>
really helpful (maybe one for 32 bit and one for 64 bit).<br>
<br>
I use the latest Windows release (yes, that from 2010!) for<br>
crosscompiling the open source CAS Maxima for Windows (using &#39;Wine&#39;=
).<br>
<br>
Now other Lisps are supported too (SBCL, ABCL), but when I started the<br>
idea, Clisp was the first Lisp compiler which worked. And it is still<br>
included.<br>
<br>
I have some code to crosscompile (using Linux as build host) Clisp (and<br>
the required libraries) for Windows, but it does not work now.<br>
<br>
Best regards, Wolfgang<br>
<br>
<br>
_______________________________________________<br>
clisp-devel mailing list<br>
<a href=3D"mailto:[email protected]" target=3D"_blank" rel=
=3D"noreferrer">[email protected]</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/clisp-devel" rel=3D=
"noreferrer noreferrer" target=3D"_blank">https://lists.sourceforge.net/lis=
ts/listinfo/clisp-devel</a><br>
</blockquote></div>

--000000000000145f6a05af30c12b--


--===============5575562872779320105==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============5575562872779320105==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============5575562872779320105==--