Any of the following linters:
After installing, make sure that it is available on the $PATH. E.g for ghdl:
$ which ghdl /usr/bin/ghdl
The simplest way to configure different linters is through M-x customize-group RET vhdl-ext-flycheck.
You can add extra directories to search for additional entities through some of these variables. For example:
(setq vhdl-ext-flycheck-ghdl-include-path '("/opt/ghdl_Xilinx_lib"))
GHDL can also look for entities in the list of current open VHDL files and directories. To enable this functionality:
(setq vhdl-ext-flycheck-use-open-buffers t)
Finally, you can add extra arguments to the VHDL linting command through the variable vhdl-ext-flycheck-ghdl-extra-args. E.g:
;; Warns if a design unit replaces another design unit with the same name
(setq vhdl-ext-flycheck-ghdl-extra-args '("-Wno-library"))
This linter needs a config file named vhdl_lang.toml in the project root, with information about the files and libraries that have to be parsed.
It will parse all the files found according to the vhdl_lang.toml config file and show the errors of current buffer, if it has any.
This linter requires no additional config.
Under the hood it runs a server for current project that parses all the found files. Client will connect automatically on buffers with flycheck enabled to retrieve the list of errors.
vhdl-ext-flycheck-mode is bound by default to C-c C-f.prefix-arg C-u C-c C-f it allows selection of current active linter.RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4