Apple are switching to ARM for their machines, abandoning Intel and x86: https://www.apple.com/newsroom/2020/06/apple-announces-mac-transition-to-apple-silicon/ Backwards compatibility is unclear at this point, but given that its a different architecture that will likely be limited. So we'll at some point need to switch our toolchain over to support ARM.
GCC bug for this: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96168 There is also the mess around binutils. Their assembler and linker don't even support macOS x86, much less ARM.
Jens Maus seems to want this: https://community.thinlinc.com/t/does-thinlinc-support-mac-m1/277
https://www.phoronix.com/scan.php?page=news_item&px=GCC-12-Apple-M1-Port-Plan
There have apparently been improvements in GCC's Apple Silicon support. Is there any update on the ThinLinc client? I'm waiting on an Apple Silicon version of the client so I can put a new workstation in service.
As mentioned in the community discussion above, gcc support seems to still be experimental. So, we need to wait for a stable release, and there is also the work to actually integrate new versions in to our build system.
Did a quick performance test now that TigerVNC has M1 builds: https://github.com/TigerVNC/tigervnc/issues/1434#issuecomment-1378736309 There was surprisingly little difference between native and Rosetta.
This project contains a proof-of-concept Linux-based build system able to target recent macOS SDK versions, as well as combining x86 and ARM binaries into a universal binary that runs natively on both Intel x86 and Apple M1 ARM: https://git.cendio.se/cendio/macos-toolchain
