-
Notifications
You must be signed in to change notification settings - Fork 75
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
Installing language server on Windows #889
Comments
The instructions for compiling from sources using opam on cygwin has this bullet point:
To successfully run that script from Command Prompt I had to set the
Then the script can be run:
The script launches a Bash terminal where the
I hope this gets smoother in the future. I don't think the average Window user of Coq can be expected to jump through these hoops. |
This does seem fairly convoluted. Also, I noticed this somewhat discouraging note in the build instructions:
Is this the easiest option to get VsCoq working natively on Windows or is there some better alternative? Is it better to just use WSL and live with the extra layer of virtualization? |
I think we should ship vscoq in the platform binary installers. Note that building the entire platform takes time, but you can easily select a smaller portion of it. |
Yes there are plans to ship vscoq in the platform binary installers. It should happen in the not so distant future ! This will make the experience much smoother. |
I am trying to use VsCoq with the new language server and Coq installed using Coq Platform on Windows (not WSL). The readme (https://github.com/coq-community/vscoq?tab=readme-ov-file#installing-the-language-server) recommends installing Coq and the language server with opam, but I don't use or have opam, because I installed Coq using the Coq Platform installer.
What is the intended way to install the language server in this case? Am I forced to use opam? Does opam even work on Windows without WSL (I've found a lot of conflicting info about this online)? Is my setup just unsuported?
The text was updated successfully, but these errors were encountered: