List all architecture variants so users can choose independently - #6
Merged
Conversation
…tly. e.g.: the x64 version can run on arm64 in Rosetta mode, enabling dependencies that do not provide an arm64-simulator build to run on the simulator.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For macOS on the arm64 architecture, installing the arm64 build of Flutter (Dart) allows arm64 applications to run in the simulator.
However, if the application is built for x64 (for example, a dynamic or static library that lacks the arm64-simulator architecture), it cannot run in the simulator.
In that case, the x64 build of Flutter (Dart) and Rosetta must be installed so the application can run in the simulator.
Therefore, both arm64 and x64 builds of Flutter (Dart) are useful, and users should be able to choose or switch between them.