-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
Extensions: Distribute ARM64 binaries #98818
Comments
@joaomoreno dotnet/vscode-csharp#3006 can be used to track the C# extension. |
I should also add - there is not currently an ARM64 .NET Core SDK Installer. I believe dotnet/core#3765 tracks that. Without that, the experience will be a bit clunky. |
Linux ARM/ARM64 support are targets for the next release of our C/C++ extension: microsoft/vscode-cpptools#429, microsoft/vscode-cpptools#2506 ; however, we've only seen around 1% of the feedback for ARM being for Windows (Surface Pro X), with 99% of the requests (seemingly) being for Linux, so we were not planning to do any work for Windows ARM -- but now it sounds like we should. I've only started preliminary investigation, so not sure how much time it will actually take to finish yet for Linux or Windows ARM (hopefully in June), and the debugger component is being tracked separately. Are there any plans for VS Code Linux ARM support (#6442)? Looks like that's only shipping in the alternate headmelted/vscodium distros that don't support the remote extension or our C/C++ debugging experience (which is restricted to VS Code). UPDATE: I was confused about local versus remote in regards to VS Code Linux ARM support (i.e. VS Code on x64 remoting to Linux ARM is supported), so local Linux ARM support doesn't matter as much. |
Is this in a development branch or something? My VS Code 1.46.0 says "unsupported architecture arm64" when I use a macOS client and remote ssh to a Linux/arm64 box. |
@rossburton It's available with the VS Code Insiders build, see https://code.visualstudio.com/updates/v1_46#_windows-arm64-insiders , https://code.visualstudio.com/insiders/ |
That says arm64 on Windows, whereas I care about Arm64 on Linux for extensions. How I use it is macos for the actual UI, connecting to a remote linux/arm64 server. |
@rossburton Oops, sorry for my confusion. What extension is giving the "unsupported architecture" message? Our C/C++ extension is working on remote arm/arm64 support for Linux, so if VS Code itself is giving that error, then that would be blocking for us. |
It appears to be the C/C++ extension. |
@rossburton Oh, your description threw me off -- we show "Architecture is not supported" (or a translated version of that). We're tracking that with microsoft/vscode-cpptools#429 and microsoft/vscode-cpptools#2506 (we're working on ARM first, followed by ARM64). |
Closing this on our part, since there is no action to do for us. Issue will remain open for discussions. |
Related to: #98587
Hi extension authors! 👋 This issue's purposed is to reach out to extensions which ship native node modules and let you know that we'll start shipping Code on Windows on ARM for Insiders now and Stable later.
Even though extensions can keep having native x86 *.node dependencies, it is ideal that you'd ship ARM dependencies instead. This can easily be achieved by running
npm install
with an environment variablenpm_config_arch=arm64
, Visual Studio should be able to handle the recompilation for you.Here are top extensions which are known to possibly download native node modules at runtime:
Here are the top 1000 extensions in the Marketplace which include substantial native node modules:
We would appreciate if you could let us know if you have addressed this and whether you hit any snags. If you end up creating an issue on your issue tracker, also let us know so we track it too. Thanks! 🙏
The text was updated successfully, but these errors were encountered: