-
Notifications
You must be signed in to change notification settings - Fork 16
Open
Description
I have a lib of models in a separate tree of code; for example.
c:\mylib\therom\rom.v
c:\mylib\74574\hct74574.v
In icarus I include "-I c:\mylib" and this allows an import syntax like ...
`include "therom/rom.v"
Whilst this works fine in icarus, this does not scan in the VSCode plugin.
"systemverilog.includeIndexing": [
"**/*.v",
"C:\\mylib"
],
Also this does not work...
"systemverilog.includeIndexing": [
"**/*.v",
"C:\\mylib\\**\*.v"
],
The problem is the scan results don't remember their relative path. So for the second example above this DOES work ...
`include "rom.v"
... but that's no use to me as it doesn't work readily in icarus.
Also ... when using the second approach then I can't navigate to symbol in the import but that's academic as the scanner doesn't work the way icarus does.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels