-
Notifications
You must be signed in to change notification settings - Fork 74
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
Support dune builds #134
Comments
Thanks for posting. I guess the plan is to invoke coq*top via dune, since only dune knows the actual profile (which may not be |
It seems there is some movement to improve dune support in PG via company-coq, see cpitclaudel/company-coq#257 Is there any progress in VSCoq? |
Haven’t heard anything, and that MR seems about jump-to-definition only, which is unsupported altogether in vscoq. |
Probably one would just need to detect if the current project is a dune-project, and prepend something to the command line arguments of coqtop that tell where to look for the libraries. And one probably want to have an option in vscode to force either of he two ways instead of the auto-detection. I have never used dune. Can someone link a small project with the default setup for a dune-coq-project? |
@fakusb thanks for taking a look, here's a template project: https://github.com/palmskog/coq-program-verification-template Especially notice the caveat at https://github.com/palmskog/coq-program-verification-template#caveats We are looking to improve this situation from VSCoq perspective, so one can imagine being able to work on this project with VSCoq when the Currently, a suboptimal hack mentioned above in the OP is required. |
- Add `coqtop.useDune` and dune path to settings. - spawnCoqTop: use dune coq top - Skip `_CoqProject` when `useDune` is set. - Address review: Switch new code to const as requested
- Add `coqtop.useDune` and dune path to settings. - spawnCoqTop: use dune coq top - Skip `_CoqProject` when `useDune` is set. - Address review: Switch new code to const as requested
See also #361 |
Is there an update on this? The workaround
still works, but it took quite some time to find this issue page for the workaround. Or can we document this somewhere to make it more discoverable? |
This is still TODO. |
When using dune, currently VsCoq won't be able to find and load built
.vo
files (ditto ProofGeneral/CoqIDE).This is a known problem, but I'm filing this issue as documentation and to post the current workaround.
I'm using an issue as documentation on purpose, since this is still pretty hacky.
As confirmed by @ejgallego, the workaround is to modify _CoqProject as follows:
Beware this breaks tasks that use
coq_makefile
, but I expect on *nix one can try processing_CoqProject
withsed -e 's!_build/default/!!
before passing it to coq_makefile.The text was updated successfully, but these errors were encountered: