plplot-ada VS distributing-gcc

I've been 3D printing quite a bit lately, which has me wondering what kind of particulate emissions the printer generates. I wrote a driver for the PMS7003 laser particulate sensor and got PLplot's Ada bindings building with Alire for generating fancy charts from the data I collect. I'm working on a driver for the nRF24L01+ 2.4 GHz radio chip so that I can setup sensors in places where wiring is difficult.

GCC 13.1.0 for aarch64-apple-darwin21, both native and cross-compiling to arm-eabi. Had to make a second release of both, because libgmp.dylib had a very unhelpful runpath setting.

Libadalang2xml now in Alire. NB, if you’re on macOS, you’ll need one of the packages I’ve been building; alr/macOS can’t build langkit, libadalang.

Yes: see here.

This is why, when considering whether to build & release a nn.2.0 macOS version, I’ll only do so if there’s a good reason: for example, GCC 12.1.0 couldn’t compile C source on macOS Ventura (version 13).

Over at Github, I’ve released GCC 12.2.0 for macOS: x86_64 for Intel Macs, aarch64 for Apple silicon. I have an arm-eabi build too, must get round to releasing it.

XNAdaLib is a large set of ready to use Ada libraries prebuilt with GNAT FSF 12.1 for macOS.

For the next few years you’ll be able to run x86_64 binaries on Apple silicon. I produced an aarch64 package based on GCC 12.1.0, see here, but (a) GCC 12.1 won’t compile C code on Ventura, (b) if you want an ecosystem try Alire whose default toolset includes a GCC 12.2-based compiler, albeit x86_64!