-
Notifications
You must be signed in to change notification settings - Fork 256
Closed
Description
Right now, the artifacts generated by taskcluster are all built for Intel Macs (note that the rust.targets there only have darwin)
If we would like our android release to be accessible by M1s, we should probably change our taskcluster configs a little. I'm not sure the full extent of what's needed, but at the minimum:
- Most likely need to split the taskcluster job for
desktop-macosinto two, one for M1s and one for Intel (including modifying thedesktop-macosscript to handle M1s. - Include
darwin-aarch64in https://github.com/mozilla/application-services/blob/main/taskcluster/ci/module-build/kind.yml#L43 - Add a
rust add target aarch64-apple-darwinin https://github.com/mozilla/application-services/blob/main/taskcluster/scripts/toolchain/cross-compile-setup.sh#L33 - Properly set the environment variables like is done in https://github.com/mozilla/application-services/blob/main/taskcluster/scripts/toolchain/cross-compile-setup.sh#L2-L11 (this will probably look something like:
export ORG_GRADLE_PROJECT_RUST_ANDROID_GRADLE_TARGET_AARCH64_APPLE_DARWIN_NSS_STATIC=1
.
.- There are most likely more changes that need to be done, but this is hitting the end of my familiarity with taskcluster
- Check-in with the taskcluster team to make sure all is OK, but if we can get an M1 to run a release megazord artifact, then we should be good
┆Issue is synchronized with this Jira Task
┆Epic: Important backlog
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels