DVT IDE for VS Code SystemVerilog User Guide
Rev. 24.1.15, 10 July 2024

4.4 Auto-config

Particularly for small projects, in order to simplify project configuration, instead of explicitly specifying lists of files, incdirs etc., you can use one or more +dvt_init_auto directives in default.build. For example:

# Identify and compile sources from the project directory

# Identify and compile sources from some other path

DVT scans the specified directories and automatically detects how to compile the source code files. For each +dvt_init_auto directive, a corresponding default.build.auto.# file is created. The .build.auto.# files contain compilation directives like incdirs, top files, libraries, UVM libraries, Xilinx libraries, etc. resulting from the auto-configuration algorithm. After scanning, DVT compiles the code using the directives in generated auto files.

Tip: You can specify multiple scan roots using +dvt_autoconfig_scan_root_add+<root>, for example when sources reside in multiple independent locations:

# Specify scan roots in addition to the compilation root

Note: The compilation root is by default an auto-config scan root. To override this behavior, specify the +dvt_autoconfig_scan_root_clear directive first:

# Don't scan the default compilation root, only the specified scan roots

DVT automatically detects and analyzes existing Intel(Altera) Quartus or Xilinx ISE/Vivado projects in the compilation root directory of a +dvt_init_auto directive. For more details see FPGA Support.

NOTE: Auto files are overwritten on every full build.

You can specify additional directives in +dvt_init_auto sections. They are copied as is in the corresponding .build.auto.# file. For example:


You can specify a compatibility mode and use simulator specific directives:


The available compatibility modes are: dvt, ius.irun, vcs.vlogan and vcs.vhdlan. If a compatibility mode is not specified, it defaults to dvt. See Compatibility Modes for a detailed description.

TIP: When working with large filesystem hierarchies or slow network drives, the scan phase might time out, by default after 40 seconds. To increase the timeout for a particular +dvt_init_auto section, use +dvt_autoconfig_timeout build config directive. For example to set timeout to 2 minutes:


TIP: Use the +dvt_autoconfig_debug+SCAN build configuration directive to see detailed scanning progress reported in the Console View.