You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Alright, this is not easy.
I think that there is no Flutter engine built by google for riscv64, and I've heard that the Google Flutter team doesn't want to build an engine for riscv64.
Maybe that will make you want to drop risc-v support ?
The dart SDK builds binaries for riscv64, so a first step would be to download dart SDK binaries directly from upstream dart and not the flutter engine. But then we still miss the Flutter engine.
Another way is to use the patches mentioned in the articles linked in flutter/flutter#99963. However I'm not sure if you want to do that, and there is still no flutter engine available in binary form.
Another way would be to use a flutter engine from another place than google, that would be maintained by the community or another organization. I plan to investigate building a flutter engine for riscv64, trying to automate that build, and we will see how that goes. I will communicate more when concrete plans are in place.
I'm not sure what you think as a maintainer of fvm, whether that seems like a total waste of your time for 0.1% of users or if you are willing to introduce special cases and dedicate a bit of time for that. But I think that if you want to support RISC-V, it might be more complex than initially thought.
Before creating a bug report please make check the following
Describe the bug
On RISC-V, fvm downloads
arm64version of the dart SDK. This will not work...To Reproduce
Steps to reproduce the behavior:
apt update && apt install -y unzip(cf. [BUG] Fail agressively when SDK setup fails (e.g. missing dependencies) #968).fvmrcfile:echo '{ "flutter": "3.35.3" }' > .fvmrc./fvm installExpected behavior
fvm downloads
riscv64binaries, and notarm64ones.Logs
Desktop (please complete the following information):
Additional context
Alright, this is not easy.
I think that there is no Flutter engine built by google for riscv64, and I've heard that the Google Flutter team doesn't want to build an engine for riscv64.
Maybe that will make you want to drop risc-v support ?
The dart SDK builds binaries for riscv64, so a first step would be to download dart SDK binaries directly from upstream dart and not the flutter engine. But then we still miss the Flutter engine.
Another way is to use the patches mentioned in the articles linked in flutter/flutter#99963. However I'm not sure if you want to do that, and there is still no flutter engine available in binary form.
Another way would be to use a flutter engine from another place than google, that would be maintained by the community or another organization. I plan to investigate building a flutter engine for riscv64, trying to automate that build, and we will see how that goes. I will communicate more when concrete plans are in place.
I'm not sure what you think as a maintainer of fvm, whether that seems like a total waste of your time for 0.1% of users or if you are willing to introduce special cases and dedicate a bit of time for that. But I think that if you want to support RISC-V, it might be more complex than initially thought.