Skip to content
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

handling external compilation #768

Open
vzaliva opened this issue May 6, 2024 · 1 comment
Open

handling external compilation #768

vzaliva opened this issue May 6, 2024 · 1 comment

Comments

@vzaliva
Copy link

vzaliva commented May 6, 2024

Currently, it's challenging to use VsCoq for Coq development involving multiple inter-dependent (.v) modules. Since it doesn't compile them (an issue possibly addressed by #252), one must compile through an external build system like dune (as discussed in #134) or make.

However, when files are recompiled outside VSCode, it fails to recognize changes in .vo files and continues to display errors based on old definitions. There are a few potential fixes for this:

  1. A minimal solution could be to force the reloading of all .vo files when the compilation is done via the Terminal -> Run Build Task menu.

  2. A more sophisticated solution would be to monitor .vo files and reload them once they change. This would allow for running dune build --watch externally, which would automatically recompile changed files, with VsCoq then picking up these changes automatically as well.

@vzaliva
Copy link
Author

vzaliva commented May 6, 2024

Sorry, I forgot to mention: I am using VsCoq v2.1.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant