You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Publish prebuilt macOS binaries for AURA so users on macOS can run aura-web-server and aura-cli without building from source.
Motivation
Release artifacts are currently only available for Linux. macOS users have no prebuilt option and must compile the project themselves, which is a meaningful barrier to getting started and to local development.
Request
Provide downloadable macOS binaries for both aura-web-server and aura-cli, covering:
Apple Silicon (arm64)
Intel (x86_64)
Acceptance criteria
macOS binaries for aura-web-server and aura-cli are published alongside the existing Linux artifacts in releases.
Both binaries run on a clean macOS machine (Apple Silicon and Intel).
So I'm able to cross compile aura from rocky9 amd64 to arm64 and darwin with cargo-zigbuilder, but unfortunately it looks like a couple of our dependencies are linking against some proprietary MacOSX libraries:
= note: warning: unable to open library directory '/opt/usr/lib': FileNotFound
error: unable to find framework 'Security'. searched paths:
/opt/System/Library/Frameworks/Security.framework/Security.tbd
/opt/System/Library/Frameworks/Security.framework/Security.dylib
/opt/System/Library/Frameworks/Security.framework/Security
error: unable to find framework 'SystemConfiguration'. searched paths:
/opt/System/Library/Frameworks/SystemConfiguration.framework/SystemConfiguration.tbd
/opt/System/Library/Frameworks/SystemConfiguration.framework/SystemConfiguration.dylib
/opt/System/Library/Frameworks/SystemConfiguration.framework/SystemConfiguration
error: unable to find framework 'CoreFoundation'. searched paths:
/opt/System/Library/Frameworks/CoreFoundation.framework/CoreFoundation.tbd
/opt/System/Library/Frameworks/CoreFoundation.framework/CoreFoundation.dylib
/opt/System/Library/Frameworks/CoreFoundation.framework/CoreFoundation
Apple specifically prohibits using any part of their SDK on non-apple hardware so this would be a legal blocker that prevents us from cross compiling from linux to mac. We'll have to use a mac runner to build the mac images.
I've manually set up and mac jenkins worker node and the latest PR is passing. I've opted to move away from zig because we're not really doing cross building anymore and making those changes just for linux amd64 -> linux arm64 seemed like a bit overkill. We can always revisit zig if we want to target other platforms/architectures.
Next steps at this point are
Confirm pipeline changes with the team
Cement the new mac worker node in our internal tooling, right now it's a manually created EC2 instance and is manually connected to Jenkins
We can also merge the PR after just step 1 so we can start delivering binaries asap!
Activity
[-][FEATURE]: Provide macOS binaries for aura[/-][+][FEATURE]: Provide macOS binaries[/+]feat(build): add macos release binaries
jakedipity commentedon Jun 30, 2026
So I'm able to cross compile aura from rocky9 amd64 to arm64 and darwin with cargo-zigbuilder, but unfortunately it looks like a couple of our dependencies are linking against some proprietary MacOSX libraries:
Apple specifically prohibits using any part of their SDK on non-apple hardware so this would be a legal blocker that prevents us from cross compiling from linux to mac. We'll have to use a mac runner to build the mac images.
feat(build): add macos release binaries
feat(build): add macos release binaries
feat(build): add macos release binaries
feat(build): add macos release binaries
feat(build): add macos release binaries
feat(build): add macos release binaries
feat(build): add macos release binaries
jakedipity commentedon Jul 8, 2026
I've manually set up and mac jenkins worker node and the latest PR is passing. I've opted to move away from zig because we're not really doing cross building anymore and making those changes just for linux amd64 -> linux arm64 seemed like a bit overkill. We can always revisit zig if we want to target other platforms/architectures.
Next steps at this point are
We can also merge the PR after just step 1 so we can start delivering binaries asap!
feat(build): add macos release binaries
feat(build): add macos release binaries
feat(build): add macos release binaries
feat(build): add macos release binaries
feat(build): add macos release binaries
feat(build): add macos release binaries
feat(build): add macos release binaries
feat(build): add macos release binaries
feat(build): add macos release binaries
chore: add darwin support to install script and update readme
chore(ci): clean up cargo cache after every macos step