Pierrick Bouvier

For now, the PR adding arm64 native build is abandoned https://github.com/flutter/flutter/pull/113928. After discussion with @stuartmorgan (see PR), artifacts for this platform is a requirement before going further. For the people...

@stuartmorgan Windows on Arm can be deployed as a VM (for free) using one of those possibilities: - KVM based virtual machine - UTM based virtual machine (on apple M1/M2...

Good news! flutter engine can be easily cross compiled without any modification on an x64 machine: ``` python3 ./flutter/tools/gn --no-goma --windows-cpu arm64 ``` Results in those files: ``` analyze_snapshot.exe: PE32+...

Thanks @loic-sharma. I'll open a different issue (for engine artifacts - https://github.com/flutter/flutter/issues/115983) and try to make a patch on that recipe.

@loic-sharma Tried to create a gerrit change for that, but it confirms I don't have access. The commit to upstream is [here](https://github.com/pbo-linaro/flutter-recipes/commit/d6323c224b04633630cff44fb3e2ef77e4f98458), based on what was done for darwin-arm64.

Thanks @loic-sharma . No problem, you said you were out :) I pushed two other commits [here](https://github.com/pbo-linaro/flutter-recipes/tree/artifacts_arm64), to fix the issue you mentioned (regarding font), and removed the embedder package...

I removed the font subset as it does not seem to be built when building for windows-arm64. Still [here](https://github.com/pbo-linaro/flutter-recipes/tree/artifacts_arm64).

Ok great! I squashed all commits, and rebased it on top of master. Could you submit it for review please, and post the link here?

Thanks, I'll answer on CL from now.

From CL, it appears the "recipes" approach will be dropped in favor of a new solution, directly integrated in flutter engine repo, from January 2023. Thus, this seems to be...