-
Notifications
You must be signed in to change notification settings - Fork 69
[native_toolchain_c] Support MSVC arm64 toolchain #167
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
Conversation
I think we have to rely on you testing this locally inside flutter_tools on an arm64 Windows host.
I wouldn't think so, but you can try adding a test and see if the arm64 executables can be found on the Windows bot. |
Ok. Locally I can test this, no problem. I'll try to add a new test here to see if it works on windows-x64 hosts. |
Please bump the version in the pubspec and add an entry to the changelog.md for that. |
Will do once you're okay with changes and tests are passing. |
Updated tests to see how it goes. |
PRs are squashed on merge in most (or all) of Dart/Flutter repos. |
Hm, seems like we have a bunch of failures due to #161 (comment). |
I have retracted package:native_assets_cli v0.3.1, try pushing a commit. |
No problem, I rebased on top of commit parent of #161. |
Tests were successful, so arm64 toolchain is available on runners 👍. |
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.
Implemented changes required by open discussions. |
See the bots: we have some analysis failures:
|
Fixed, |
Thanks @dcharkes for quick interactions, that was a fun ride! |
Will the new version for |
I've created a release+tag. It should be published automatically now. |
I can use it now, perfect! Thanks |
Well, thank you! 🙏 |
Bumps [actions/setup-java](https://github.com/actions/setup-java) from 19eeec562b37d29a1ad055b7de9c280bd0906d8d to 308abcba03229002f0055e17d79d00c32fca160f. - [Release notes](https://github.com/actions/setup-java/releases) - [Commits](actions/setup-java@19eeec5...308abcb) --- updated-dependencies: - dependency-name: actions/setup-java dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [actions/setup-java](https://github.com/actions/setup-java) from 19eeec562b37d29a1ad055b7de9c280bd0906d8d to 308abcba03229002f0055e17d79d00c32fca160f. - [Release notes](https://github.com/actions/setup-java/releases) - [Commits](actions/setup-java@19eeec5...308abcb) --- updated-dependencies: - dependency-name: actions/setup-java dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
This PR adds support to be able to compile native-assets on windows-arm64.
It seems to be what is needed to compile windows-arm64 flutter apps, as discussed initially here.
@dcharkes I'm not sure which tests to update exactly. Since windows-arm64 runners are not available for this repository, will we still be able to test this? In more, do existing x64 runners have installed msvc arm64 toolchain?