macOS builds need to be M-arch based

[josephwright]

The current build pipeline for macOS produces Intel binaries: those are going to cease to be supported soon, so if the intention is to continue to work on macOS, an M-arch based build will be needed.

[bgvoisin]

There was an ARM build of TeXworks 0.6.10 for macOS, but it seems to have been abandoned for 0.6.11. I assume this was because of the signature-related crash in issue #1075.

There was a similar crash for the experimental ARM build of FontForge. It seems signature requirements are more stringent for ARM apps than for Intel. The details are way beyond me, but the developers there have just (as in last week) found a way to get adhoc-signed ARM apps to run on macOS, ie get rid of the crash. See fontforge/fontforge#5834.

I have no idea whether their solution can be adapted to TeXworks. I tried to read it, but that's mostly klingon to me.

About the schedule for Intel deprecation, as I've seen confusing info here and there on the web:

• Current macOS is 26 Tahoe, released in Autumn 2025. It runs on both Intel and ARM Macs. On the latter, Intel apps run thanks to the built-in Rosetta binary translator.

• macOS 27 Golden Gate has been in developer beta for two weeks, and will be released in Autumn 2026. It only runs on ARM Macs, but still includes Rosetta. So the current x86_64 TeXworks runs on it, though the warnings about Intel deprecation become way more frequent.

• macOS 28, to be released in Autumn 2027, will no longer include Rosetta. So there will be no way to run Intel apps on it.

Here's what happens right now launching TeXworks 0.6.11 for the first time on macOS 27. TeXworks launches successfully, but a notification appears: