Re: basic GitHub action for building CCL lisp kernel?
Ron Garret <[email protected]> Fri, 11 Aug 2023 09:07:32 -0700
| Newsgroups | gmane.lisp.openmcl.devel |
|---|---|
| Message-ID | <[email protected]> |
I don't have any experience with github actions, but I do have spare bandwidth, a fair bit of experience running stuff in the cloud, and a willingness to read docs. Apropos of which, according to the CCL docs there are 8 platforms: reasonably recent macOS (x86-64) Linux (x86, x86-64, armv7l) FreeBSD (x86-64) Solaris (well, illumos) (x86-64) Microsoft Windows XP and later (x86, x86-64) But you said six. Which platforms have been dropped? rg > On Aug 10, 2023, at 9:10 PM, R. Matthew Emerson <[email protected]> wrote: > > I think it would be useful have some kind of automated system that can compile the CCL lisp kernel (a C and assembly language program) on all of the platforms and report whether that worked. > > So, if there are any changes in $repo/lisp-kernel, I’d like to trigger an automated build of all the lisp kernel platforms that I can. > > Does anyone have experience doing this with GitHub Actions? If so, would you be willing to offer some tips? > > Years ago, I had Buildbot set up and running fairly well, but I don’t want to spend time on that right now, especially if I can leverage GitHub services. > > My long-term dream would be to have an automated way to make release binaries. As it stands, I just got through building and packaging the 1.12.2 release for all six platforms by hand. But I’d be happy to start with baby steps. > >