Failed to run vhdl_ls, when opening the project folder

[ndr-lmnc]

Hi, I have installed this extension since I wanted to work on my Mac on some VHDL code using GHDL. For me having the syntax highlighted is already a lot, but all the times I open my project the error mentioned in the title appears, and when I open the error for details I see the following.

Language server error: vhdl_ls

no asset found matching "vhdl_ls-x86_64-apple-darwin.zip"
-- stderr--

My computer is a MacBook Pro 2019, and I'm running Sequoia. I'm not sure if the problem is from my side and if I have to install something or do anything.

[rapgenic]

Hi @ndr-lmnc, thanks for the report. I suspect that there is no build for the darwin x86_64 architecture (only aarch64, aka ARM) of the vhdl_ls language server (see also the release page for the last version for example, https://github.com/VHDL-LS/rust_hdl/releases/tag/v0.83.1).

Sadly I do not have a mac to test this on... Something you could do is try the corresponding vscode extension (https://marketplace.visualstudio.com/items?itemName=hbohlin.vhdl-ls) and see if that works on your mac. In that case we can find out what what binary it's downloading and fix the zed extension correspondingly

[ndr-lmnc]

Hi @rapgenic, Thanks for helping. Sadly, we have also had no success on Vscode. Still, problems with the plugin started there. I have checked the versions that I think the extension downloaded, and they are not even for any version of Mac.

vhdl_ls-x86_64-pc-windows-msvc
vhdl_ls-x86_64-unknown-linux-musl

Since then, I have checked on the rust_hdl_vscode for issues about this and there is one issue open about MacOS not working on vs code: VHDL-LS/rust_hdl_vscode#73
I have also checked the on rust_hdl, and I have found 2 closed issues that don't fit the same problem that I am having, at least I think.
I have also seen that in the releases for the rust_hdl there is apple darwin but for platform aarch64, that I think should be the Apple Silicon library and not the one for x86_64. Maybe I should make an issue also there asking for support for this architecture and check later for a possible new release?