-
Notifications
You must be signed in to change notification settings - Fork 56
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
vscode extension not starting on nixos #321
Comments
I can see three possible solutions to this, from easiest to hardest to do:
What do you think @elijah-potter? |
If memory serves, this is what most extension does even if they have an option to use a "bundled" binary in the extension. I can see how this would defeat the purpose of bundling the binary, but I instead think of it as adding another option. The default (to cater most os) imo is to still use the bundled binary.
IIRC rust analyzer does this, but I think it would put a burden on your side for maintaining each OS. The first option should suffice.
I think the binary found glibc, I ran this command on the bundled binary and got the libraries except for one, the libstdc++ one.
|
Interesting. I thought any dynamically linked binary wouldn't be able to resolve its dependencies in NixOS because of how immutable distos work, but only the C++ standard library (libstdc++) is missing. Anyway, I was probably overthinking this. I guess exposing a setting would suffice. I'll try to get a PR up soon. |
Hi @tengkuizdihar, by the next release, you can set If you have some time and would like to give it a try now, you can try following the "Packaging and Installing the Extension" section of the Development Guide. |
thank you @mcecode |
It works! @mcecode |
The extension is not running on nixos, because this OS doesn't play nicely with dynamically linked libraries from third parties. There's already harper-ls and harper-cli in nix package registry, is there a way for me to change the path of the language server in harper? Below is the log from the extension.
The text was updated successfully, but these errors were encountered: