[Openmcl-devel] basic GitHub action for building CCL lisp kernel?

[R. Matthew Emerson]

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.