-
-
Notifications
You must be signed in to change notification settings - Fork 76
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
iverilog linter does not work on macos with vscode 1.76.2 #407
Comments
[EDITED] |
I have the same issue, I tried to clear "verilog.linting.linter" but it still doesn't works. Can you please give me any other possible solutions? |
Make sure you have added the installation path of iverilog to PATH if you are using windows. |
I'm using macOS. And I have set "Verilog > Linting: Path" to "iverilog". Is that the right PATH ? |
Sorry, I made a mistake, it's clear "verilog.lingting.path" instead of "verilog.linting.linter" |
草,你也是中国大学生,直接用中文吧,我现在"verilog.lingting.path" 是空的,然后 "verilog.linting.linter" 是 "iverilog",是这样配置的吗 |
我的mac也不行,,同样的配置,windows就修复了,我以为mac也可以。怎样配置路径都不可以 |
谢谢兄弟,学电信的用macOS太折磨了 :( 我用英文反馈一下 bug 吧。 |
Unfortunately, linter still doesn't work on macOS. No matter what configuration is. According to @ @devindang , Windows users can try the solution he said. But linter on macOS still doesn't work. I guess there is a bug for macOS :( |
use Teros HDL instead. The linting works fine with Icarus Verilog. |
Maybe we need to change the description text of |
Is the following configuration correct?
Even I configured CTAGS paths, it does still not work. |
Teros HDL extension is too bloated, I don't want to use it. So could you please help me to configure it correctly? thanks very much. |
What do you see in the Output Window when you execute the below process?
For my environment, I can see
|
I think it's correct. |
|
|
And I tried to set verilog.linting.path to |
I didn't find "Output Window" where I can input something, but when I open command panel by
|
Both are same as my mac. |
This is my settings json
|
seems ok to me. |
Can you find the reason for the following behavior? What does 'verilog.lint' refer to?
|
I couldn't find why it happens. I guess the extension initialization process has some problem. Did you try to reinstall the extension? |
Can you find the reason of the following behavior? What does 'verilog.lint' refer to?
Yes, I have tried to reinstall the extension, but it did not work. |
I can't think of any good ideas for investigating. |
Do you see any text in the Output Window when you execute "Verilog: Return lint tool"? |
What do you see when you execute "Verilog: Rerun lint tool" on a non-Verilog/SystemVerilog file such as text, python or javascript? |
Ah, never mind. You must see "Verilog-HDL/SystemVerilog: No document opened". |
The error happens between LintManager.ts#L128 and IcarusLinter.ts#L60. |
Yes, I saw "Verilog-HDL/SystemVerilog: No document opened". |
Well, thanks a lot |
Released v1.11.2 with more logging messages. For my mac, I got this
|
I got this, and see the picture
|
Thanks. |
Yes, the following is the result.
|
I see. |
This is the outputs:
|
I could reproduce the problem on Windows. The error happens around IcarusLinter.ts#L70. When you don't open the workspace folder and you try to run lint, then you get the error. You need to open the folder when you run lint. |
I'm not going to solve the problem soon because I don't use it in such a way. I always open the workspace folder. |
The problem might be solved by enabling "runAtFileLocation" option. It forces to use the file location as the cwd. |
The problem may have been fixed in v1.11.3. |
Thank you, it gets worked now when I just open a file without opening a folder. |
Describe the bug
iverilog linter does not work on macos with vscode 1.76.2
Environment (please complete the following information):
-- color themes: GitHub dark corlorblind
-- lint tools: iverilog, 11.0
Steps to reproduce
Steps to reproduce the behavior:
Log
Attach the log generated while following the above steps
Expected behavior
A clear and concise description of what you expected to happen.
Actual behavior
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: