Repository navigation
Sign binary releases #137
Description
The pre-built Windows and macOS binary releases that we ship are very hard to use because they are unsigned, so these systems will block their execution by default. Things are now even worse as we ship various libraries due to SDL2... and these cause macOS to raise warnings for every single library. I'm not sure how we could sign the binaries, but it should be done.
For those reading, note that the binaries are built via GitHub Actions so you can audit how they are put together by looking at the scripts under .github/workflows/ and the logs for the corresponding run.
Activity
BlameTroi commentedon Jul 5, 2026
If one trusts the packaged builds here, and I do, run the following shell command at your terminal. It removes the quarantine flag that macOS places on anything downloaded (or unzipped from a downloaded zip). Do not use this unless you trust the source of your binaries. Check the SHA. Caveat emptor.
The use of
sudois only required for library files for SDL as they unzip without write permission, which is probably a good thing. It might also be good to remove the write attribute on the endbasic and andbasic.bin files.I'm not a serious Apple developer so I don't know if there's a better way to handle this other than signing, but this works for me.
And by the way, I had no idea endbasic existed. This is cool and I've been wanting something CLI usable that wasn't PC BASIC (a fine tool but geared for backward compatibility). Bravo!
jmmv commentedon Jul 12, 2026
Oh thanks for the tip; I forgot that this was possible. I'll add this info to the download page / README.