-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support architectures in the build/release side #682
Support architectures in the build/release side #682
Conversation
57857c6
to
1d5b1a8
Compare
launchas-osqueryi-tables: table.ext | ||
sudo launchctl asuser 0 osqueryd -S --allow-unsafe --verbose --extension ./build/darwin/tables.ext | ||
# Actual release targets. Because of the m1 cgo cross stuff, this requires explicit go paths | ||
rel-amd64: CROSSGOPATH = /Users/seph/go1.15.6.darwin-amd64/bin/go |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could this be ~/go1.14.6.darwin-amd64/bin/go
or does the path need to be that specific?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It could probably use ~
. Once there's a real m1 release, I expect we'll drop these into nicer paths anyhow
Update the build/release process to support creating darwin universal binaries. This requires building on an m1 machine, with go installed at the specified paths.
To make this a bit smoother, it also updates a handful of the abstractions across our build tools.
This will likely get smoother as the m1 ecosystem evolves.