AndrewNolte / vscode-system-verilog

HDL support for VS Code
MIT License
17 stars 1 forks source link

Linter: Iverilog command line has extra space between -t and null #1

Closed terrywwgit closed 4 months ago

terrywwgit commented 6 months ago

Describe the bug When the extension calls iverilog to lint the code an error

"C:\iverilog\bin\iverilog.exe" not found. Configure verilog.lint.iverilog.path, add to PATH, or disable in config.

The log output shows that the path is not the problem with the linter. The extension finds the iverilog.exe fine. The error reported by iverilog is that it can't find the null.conf file


Steps to reproduce

  1. Install iverilog
  2. Enable iverilog as a linter in settings

Log 2024-05-19 14:17:36.642 [info] [lint] [iverilog] linting file:///s%3A/GitRepo/xxx.v

2024-05-19 14:17:36.642 [info] [lint] [iverilog] Running $s:\GitRepo\xxx: C:\iverilog\bin\iverilog.exe -t null -g2005 -Is:/GitRepo/xxx s:/GitRepo/xxx.v

2024-05-19 14:17:36.700 [error] [lint] [iverilog] Error: Command failed: C:\iverilog\bin\iverilog.exe -t null -g2005 -Is:/GitRepo/xxx s:/GitRepo/xxx.v

ERROR: Unable to read config file: C:\iverilog\lib\ivl\ null.conf

Expected behavior vscode highlights errors in code

Actual behavior No highlights, error is reported stating that the iverilog.exe executable can not be found.

Additional context The iverilog.exe is in my path, and the error occurs even when the full path is configured in extension settings.

AndrewNolte commented 4 months ago

Fixed in 9.15