Been working quietly but making headway on reviving the Mac binary build, learning what all we need to do to ship a proper installer. Our old make_pkg and make_dmg scripts where both out of date (pkg more than dmg), but the biggest glaring omission is code signing. The build is clean and is passing make test across the board (for 7.40.2 and latest). Working now to sign the binaries+libs, pkg installer, and dmg, as well as what script or cmake updates we can make to help automate this.
out of curiosity... I'm assuming code signing means an SSL cert, can the site cert or one generated by eff certbot work?
if it's an apple dev cert, I think that's $100/yr
I'm still reading through their dev docs, but from what I could tell -- looks like it's possible to create a self-signed trustable binary app that at least avoids all the warnings and restrictions on download. I think it might still require registering the cert with apple, but unclear if that's a general requirement.
Last updated: Aug 07 2025 at 01:01 UTC