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
A bit of an experience report: I successfully compiled the VS Code extension on ARM Mac OS using Nix. However, the extension did not work when installed because it couldn't find the LSP executable.
The reason seems to be that the LSP executable was named superbol-free-linux-x64, but the extension couldn't find it under that name even though it was in the correct _dist directory.
Workaround: The file should renamed from $HOME/.vscode/extensions/ocamlpro.superbol-0.1.5/_dist/superbol-free-linux-x64 to $HOME/.vscode/extensions/ocamlpro.superbol-0.1.5/_dist/superbol-free. After that, things work fine.
Relatedly, the VSIX file generated by the build process also ends up being called superbol-vscode-platform-0.1.5-linux-x64.vsix for some reason.
A bit of an experience report: I successfully compiled the VS Code extension on ARM Mac OS using Nix. However, the extension did not work when installed because it couldn't find the LSP executable.
The reason seems to be that the LSP executable was named
superbol-free-linux-x64
, but the extension couldn't find it under that name even though it was in the correct_dist
directory.Workaround: The file should renamed from
$HOME/.vscode/extensions/ocamlpro.superbol-0.1.5/_dist/superbol-free-linux-x64
to$HOME/.vscode/extensions/ocamlpro.superbol-0.1.5/_dist/superbol-free
. After that, things work fine.Relatedly, the VSIX file generated by the build process also ends up being called
superbol-vscode-platform-0.1.5-linux-x64.vsix
for some reason.I found the workaround after looking at
superbol-studio-oss/src/vscode/superbol-vscode-platform/superbol_languageclient.ml
Lines 43 to 54 in 922588f
Hope this helps, and thanks for making this extension!
Aside: To emphasize, the LSP executable that was built was in fact a darwin-arm64 executable despite the name:
The text was updated successfully, but these errors were encountered: