Skip to content

☂️ Add support for ARM macOS as a target #60113

Closed
Closed
☂️ Add support for ARM macOS as a target#60113
Assignees
cbracken
Labels
P1High-priority issues at the top of the work lista: buildBuilding flutter applications with the toola: desktopRunning on desktopc: new featureNothing broken; request for a new capabilitycustomer: crowdAffects or could affect many people, though not necessarily a specific customer.engineflutter/engine related. See also e: labels.platform-macosBuilding on or for macOS specificallyplatform-target-armTargeting an ARM-based platformtoolAffects the "flutter" command-line tool. See also t: labels.

Description

@stuartmorgan-g
stuartmorgan-g
opened on Jun 23, 2020

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

Tracking Apple Silicon as a host device separately at #60118.

Activity

  1. stuartmorgan-g
    added
    c: new featureNothing broken; request for a new capability
    toolAffects the "flutter" command-line tool. See also t: labels.
    engineflutter/engine related. See also e: labels.
    platform-macosBuilding on or for macOS specifically
    a: desktopRunning on desktop
    a: buildBuilding flutter applications with the tool
    on Jun 23, 2020
  2. jmagman
    added
    P3Issues that are less important to the Flutter project
    on Aug 18, 2020

  3. alexmarkley commented on Sep 19, 2020

    @alexmarkley
    alexmarkley
    on Sep 19, 2020 · Hidden as off-topic

  4. stuartmorgan-g commented on Sep 19, 2020

    @stuartmorgan-g
    stuartmorgan-g
    on Sep 19, 2020 · Hidden as off-topic
    Author

  5. alexmarkley commented on Sep 19, 2020

    @alexmarkley
    alexmarkley
    on Sep 19, 2020 · Hidden as off-topic

  6. stuartmorgan-g commented on Sep 19, 2020

    @stuartmorgan-g
    stuartmorgan-g
    on Sep 19, 2020 · Hidden as off-topic
    Author

  7. alexmarkley commented on Sep 19, 2020

    @alexmarkley
    alexmarkley
    on Sep 19, 2020

    Then hopefully we should also be agreed that the place to discuss the new thing you are requesting is in the issue you filled for it, rather than this completely unrelated issue.

    @stuartmorgan I'm sorry if my misunderstanding was frustrating. Being new to the project, a plain reading of this issue left me unsure what the point of this issue was.

    That said, I'm happy to help with testing of the macOS Desktop support on Apple Silicon. Currently (flutter master from an hour ago), .app bundles produced by flutter build macos on x86_64 hosts seem to work fine on Apple Silicon under Rosetta.

    Additionally, the tooling flutter run -d macos runs fine on Apple Silicon, but obviously under Rosetta.

    As I'm sure you expected (or if you've tested this yourself, you already know) the problems start when I launch the project in Xcode and ask it to build for 'My Mac', in which case I get the following:

    error: The linked and embedded framework 'App.framework' is missing one or more architectures required by this target: arm64. (in target 'Runner' from project 'Runner')
error: The linked and embedded framework 'FlutterMacOS.framework' is missing one or more architectures required by this target: arm64. (in target 'Runner' from project 'Runner')

    My intention here is to be as helpful as possible, while trying to improve and future-proof my own app project(s). I'm new to the Dart and Flutter projects, but I'm interested in learning and contributing as quickly as possible.

    Please let me know if there is any way I can assist.

  8. TahaTesser
    added
    passed first triage
    on Oct 22, 2020

  9. GyuriMajercsik commented on Nov 24, 2020

    @GyuriMajercsik
    GyuriMajercsik
    on Nov 24, 2020 · Hidden as off-topic

  10. arnemolland commented on Nov 24, 2020

    @arnemolland
    arnemolland
    on Nov 24, 2020 · Hidden as off-topic

  11. 31 remaining items

  12. cbracken
    added 2 commits that reference this issue on Mar 17, 2022

    [macOS] Enable universal binary builds by default

    0ab2211

    [macOS] Enable universal binary builds by default (#100271)

    a618ca2

  13. cbracken commented on Mar 17, 2022

    @cbracken
    cbracken
    on Mar 17, 2022
    Member

    As of #100271, we should be building macOS universal binary apps by default on master branch.

    Note that, like all macOS apps, the default is that debug builds build as single-architecture binaries using the architecture of the machine you're working on. Profile/Release builds build as universal binaries. While it is not the default for macOS apps (Flutter or otherwise), if you want to generate universal binaries for debug builds, you can take the following steps:

    1. Select the Runner project in Xcode.
    2. Select the Runner target in the settings sidebar.
    3. Select the Build Settings tab and select All for the options to show.
    4. Expand the Build Active Architecture Only option and for Debug, change Yes to No.

    image

    Please shout if you run into any issues with this. We'd love to get feedback on any issues you encounter -- please file a new issue and link it here.

  14. cbracken
    added 3 commits that reference this issue on Mar 22, 2022

    [macOS] Add run release test in devicelab (#100526)

    4b81978

    [macOS] Ignore stderr contents in launch test

    eccc7d7

    [macOS] Ignore stderr contents in launch test (#100591)

    e827f0b

  15. jmagman commented on May 3, 2022

    @jmagman
    jmagman
    on May 3, 2022
    Member

    Closing as complete. The remaining testing work is being tracked in #87508.

  16. jmagman
    closed this as completedon May 3, 2022

  17. github-actions commented on May 17, 2022

    @github-actions
    github-actionsbot
    on May 17, 2022

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  18. github-actions
    locked as resolved and limited conversation to collaborators on May 17, 2022
  19. cbracken
    added this to Flutter Desktopon May 24, 2022
  20. cbracken
    moved this to Done in Flutter Desktopon May 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P1High-priority issues at the top of the work lista: buildBuilding flutter applications with the toola: desktopRunning on desktopc: new featureNothing broken; request for a new capabilitycustomer: crowdAffects or could affect many people, though not necessarily a specific customer.engineflutter/engine related. See also e: labels.platform-macosBuilding on or for macOS specificallyplatform-target-armTargeting an ARM-based platformtoolAffects the "flutter" command-line tool. See also t: labels.

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions