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 use case is for SystemVerilog classes and packages. Let P be the main package (./pkg.sv):
P includes the next files (classes): ./transaction/c0.sv, ./transaction/c1.sv, ..... ./transaction/c15.sv
if the class files also include some file from upper directory (../ , being the same dir that contains pkg.sv), then xvlog will create an internal path that is very long: ./transaction/../transaction/../transaction/../transaction/../transaction.......
The only solution that I found is to run xvlog from the same directory as the file being opened. This feature is already implemented for verilator linter. I went to extension man.js file, got the code from verilator implementation and used it to xvlog. Now is working Ok.
Can we have this option in the feature?
The text was updated successfully, but these errors were encountered:
Describe the bug
The use case is for SystemVerilog classes and packages. Let P be the main package (./pkg.sv):
The only solution that I found is to run xvlog from the same directory as the file being opened. This feature is already implemented for verilator linter. I went to extension man.js file, got the code from verilator implementation and used it to xvlog. Now is working Ok.
Can we have this option in the feature?
The text was updated successfully, but these errors were encountered: