Finding include files used when they're in the same folder as the main RTL file

[zigzagtx2778]

I know that can search the tree.diagnostics list for diag code CouldNotOpenIncludeFile for files not in the same location as the RTL and if the correct include directory was not specified. For include files that are in the same folder as the parsed RTL file, how do I determine the include file read in since pyslang doesn't error on these as it automatically finds them?

[MikePopoloski]

Not sure what you're asking here. If the files are found then why would you expect errors to be issued, or why is it a problem that they are not?

[svenka3]

A guess based on a recent Lint rule we developed for a team:

Some SV compilers do not find include files in same directory as the main file unless +incdir+. is specified while others do (I believe recent LRM clarified this and mandates it). Now, imagine if a team is migrating from one vendor to another such lint rules ease that process especially in large code base, distributed teams.

[MikePopoloski]

--disable-local-includes can be used to disable finding of include files relative to the source file if desired.

[zigzagtx2778]

@svenka3 nailed it. Not all tools default to including the local folder automatically. In creating my database of RTL files used in a project, include files, package import requirements, interface requirements, etc, I need to know every include file used so that I know every include folder needed to complete the compile in the other tool.