Fwd: CCL 1.13 release

GrĂ©gory Vanuxem <[email protected]> Thu, 22 Aug 2024 08:08:47 +0200
Newsgroups gmane.lisp.openmcl.devel
Message-ID <CAHnU2dYJVR44RK3qR6=SAdhBvPBoAERFtshsm+D74YrcYY21eA@mail.gmail.com>
---------- Forwarded message ---------
De : Gr=C3=A9gory Vanuxem <[email protected]>
Date: jeu. 22 ao=C3=BBt 2024 =C3=A0 08:06
Subject: Re: [Openmcl-devel] CCL 1.13 release
To: R. Matthew Emerson <[email protected]>

Hello,

First, thanks for this work!

A quick note:
https://ccl.clozure.com/download.html
needs to be updated (there is also a typo, "GitHib", in it).

A parameter to 'git clone' is also --branch or -b I think it could be
relevant in the screencast: -b v1.13

As another quick note, may be https://ccl.clozure.com/ can include the
current release number in it, I don't know

I have not checked other ccl.clozure.com pages.

Regards,

Greg

Le mer. 14 ao=C3=BBt 2024 =C3=A0 07:04, R. Matthew Emerson <[email protected]=
> a =C3=A9crit :
>
> I have just released CCL 1.13.
>
> https://github.com/Clozure/ccl/releases/tag/v1.13
>
> In addition to numerous bug fixes, this release uses https://github.com/C=
lozure/ccl-ffigen to process header files for the interface databases on Fr=
eeBSD, Linux, and Solaris-ish systems.  You may run into differences when u=
sing the #_ and #$ reader macros.  Also, many fewer header files are proces=
sed, so if your code accesses a fairly obscure foreign name, you might find=
 that it is now missing.  Please report an issue at https://github.com/Cloz=
ure/ccl/issues/new if you discover a problem.
>
> The previous interface databases are carried forward unchanged on macOS a=
nd Windows. They will be updated in a future release.
>
> As previously promised, a 32-bit x86 Lisp is again included for FreeBSD a=
nd Solaris-ish systems (in addition to the 64-bit x86 version).
>
> Please note that this release does not include support for Apple Silicon =
(ARM64) hardware. That will be in a future release.
>
> Thank you to everyone who reported bugs and sent in patches and pull requ=
ests.
>
> I would like to thank ForrestHunt, Inc. for their support.
>