-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Support Windows+arm64 #17572
Comments
Is this for a production environment that is using arm builds or for developers? cc @envoyproxy/windows-dev |
While rumors exist for cloud offerings, I don't see any windows+arm64 right now. I would say "only dev" until someone else pipes in about an IoT or server-side configuration that's possible. Gut feeling is that this will be about devs using a 2-in-1 running Qualcomm Snapdragon processors (SQ1 and SQ2). Besides me though, it is just a hunch, so take it for what it's worth. I mentioned the surface x pro (SQ2) as likely that's what I would use to verify arm works on windows, not just here but other projects. I found some tip that says certain emulation exists, but not sure it works for envoy or not. |
I know some of our toolset requires golang, so supporting this would likely become dependent on those tools building with go 1.17 or be |
I've analyzed this docker issue on the same topic for more context. I'm mentioning this mainly as knowing that our windows support is currently limited to docker packaging of it. Users here mention windows configurations beyond the Surface Pro X: Samsung Galaxy Book S, HP Elite Folio, and a server-side config, Ampere Altra. It clarifies that emulation only works for x86 apps, not 64bit. However, WSL2 may work albeit complicated and people struggle with it when installing manually. |
related this could be easier if envoy didn't depend on go #17886 |
Title: Support Windows+arm64
Description:
Similar to Apple Silicon (#16482), we should also support, or at least track desire for Surface Pro X or similar windows+arm64 builds of Envoy
The text was updated successfully, but these errors were encountered: