Build Configurations
In order to provide advanced functionality (like hyperlinks, autocomplete, design and class hierarchy, error signaling, etc.), DVT 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). As you change sources, DVT performs an incremental build (incremental compilation), that is it analyzes only the changes. Unless the DVT.buildAutomatically.enable
setting is set to false, an incremental build is performed as soon as you save or as soon as DVT detects some idle time after you changed the code.
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 folder.
“C” decorations indicate if a file is compiled, for example in the Explorer View.
This is a compiled file. |
|
This file is not compiled. |
- Project Natures
- Non-top files
- default.build
- Auto-config
- Simulator Log-config
- Emulating compiler invocations
- Multiple .build Files
- Compatibility Modes
- List of Compatibility Modes
- How to Specify the Compatibility Mode
- Paths
- Strings
- Comments
- Environment Variables
- Including Other Argument Files
- Build Persistence
- All Build Directives
- SystemVerilog OVM or UVM Library Compilation
- Xilinx Libraries Compilation
- Intel(Altera) Quartus Libraries Compilation
- Questa Libraries Compilation
- Use of External Programs