Compile

In order to provide compiler-backed information to AI agents, the DVT MCP Server analyzes the source code files in your project. This analysis process is called build and it is performed by the DVT internal builder (also referred to as internal builder or DVT builder or DVT parser). For convenience, build is synonym with code compilation or code analysis.

The internal builder performs an initial full build of your project (a full build can also be triggered on demand via dvt_build_project (available only for CLI AI agents) tool). An incremental build can also be performed via the dvt_compile_changed_files (available only for CLI AI agents) tool.

DVT includes standard compliant code parsers. During the build process it creates an internal representation of the code. This representation is called the internal DVT dictionary, index, database or model.

In order to build, the internal builder uses the arguments that you specify in the current build file. A build file is one of the <name>.build files located in the .dvt folder of your project.

• Auto-config
• Emulating compiler invocations
• Compatibility Modes
  • List of Compatibility Modes
  • How to Specify the Compatibility Mode
    • Default DVT Compatibility Mode
      • Specifying a <syntax>
      • Examples
    • gcc Compatibility Mode
    • ius.irun Compatibility Mode
      • Examples
    • ius.perspec Compatibility Mode
    • questa.vcom Compatibility Mode
    • questa.vlog Compatibility Mode
    • questa.qrun Compatibility Mode
    • vcs.vhdlan Compatibility Mode
    • vcs.vlogan Compatibility Mode
    • xcelium.xrun Compatibility Mode
      • How to specify <syntax> for - default_ext <syntax> and - <syntax>_ext directives
      • Examples
• Paths
• Strings
• Comments
• Environment Variables
• Including Other Argument Files
• All Build Directives
• SystemVerilog OVM or UVM Library Compilation
• Xilinx Libraries Compilation
• Intel(Altera) Quartus Libraries Compilation
• Questa Libraries Compilation
• Use of External Programs