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
The language server needs to know your library mapping to perform full analysis of the code. For this it uses a configuration file in the [TOML](https://github.com/toml-lang/toml) format named `vhdl_ls.toml`.
@@ -84,3 +55,17 @@ lib1.files = [
84
55
]
85
56
```
86
57
58
+
## As an LSP-client developer how should I integrate VHDL-LS?
59
+
I recommend that the `lsp-client` polls GitHub and downloads the [latest](https://github.com/VHDL-LS/rust_hdl/releases/latest) VHDL-LS release from GitHub.
60
+
61
+
VHDL-LS has frequent releases and the automatic update ensures minimal maintenance for the `lsp-client` developer as well as ensuring the users are not running and outdated version.
62
+
63
+
## VHDL Language Frontend
64
+
[](https://crates.io/crates/vhdl_lang)
65
+
### Goals
66
+
- This project aims to provide a fully featured open source VHDL frontend that is easy to integrate into other tools.
67
+
- A design goal of the frontend is to be able to recover from syntax errors such that it is useful for building a language server.
68
+
- Analysis order must be automatically computed such that the user does not have to maintain a compile order.
69
+
- Comments will be part of the AST to support document generation.
70
+
- Separate parsing from semantic analysis to allow code formatting on non-semantically correct code.
0 commit comments