☂️ Add support for ARM macOS as a target #60113
Description
Filing as an umbrella bug for the overall feature of building ARM macOS applications. We can add specific sub-issues over time, but at a high level this will involve:
- The necessary Dart support
- Building/uploading engine artifacts in the correct format
- Updating the tool to understand the new target
- potentially adding new options to control what is being targeted
Issues
- Add Mac M1 ARM machines to the prod pool #87508
- Use ARM macOS frameworks,
gen_snapshot_x64andgen_snapshot_arm64in the tool #97681 - Run macOS integration tests on M1 Macs #97977
- Add integration tests to validate architectures of built macOS app #97978
- FlutterMacOS.framework engine isn't natively available for desktop for ARM macOS Apple Sillicon (including building for all valid architectures on x86) #69221
- Adds scripts for cross-arch macOS framework engine#31014
- Adjust lipo thinning input/output for macOS #97111
- [doctor] Add macOS architecture to doctor output #65976
- macOS xcode project should move Framework linking to tool #56581
- CocoaPods compatibility with Apple DTK (Apple Silicon) CocoaPods/CocoaPods#9907
Tracking Apple Silicon as a host device separately at #60118.
Metadata
Metadata
Assignees
Labels
High-priority issues at the top of the work listBuilding flutter applications with the toolRunning on desktopNothing broken; request for a new capabilityAffects or could affect many people, though not necessarily a specific customer.flutter/engine related. See also e: labels.Building on or for macOS specificallyTargeting an ARM-based platformAffects the "flutter" command-line tool. See also t: labels.
Type
Projects
Status