Your First DVT Eclipse IDE Project

Description

This video outlines the few simple steps required for bringing up a project in the DVT GUI. See description below for links to related videos:

How to Start DVT on...
Linux - https://youtu.be/IuvBAvQUCO8
Windows - https://youtu.be/5B287Ll5twQ
macOS - https://youtu.be/gH4XlB94XzA

Build Auto-Configuration - https://youtu.be/3KrUi_83ee0

Reuse Simulator Arguments - https://youtu.be/IxP49VuqjvY

DVT CLI Project Bring-up - https://youtu.be/fic2mjOs-pE

This video was made with DVT 21.1.14.

Transcript

Prerequisites

In this video, we assume that you have already installed the DVT Eclipse IDE from a distribution, have the license keys, and that the DVT_HOME and DVT_LICENSE_FILE variables are properly set up.

Starting DVT Eclipse IDE

To start DVT, run the DVT_HOME/bin/dvt.sh script. When asked for a workspace, provide an empty or even non-existing directory, as it will be created automatically. When starting DVT again, the last workspace used will be automatically filled into the dialog.

Creating a New Project

To create a project, go to File -> New -> DVT Project. Usually, the project location is the directory where your source code resides. Next, pick the languages that you plan to use.

If the source files are mixed with numerous artifacts, such as regression results, generated documentation, cell libraries, and so on, in order to avoid platform slowdowns, the tool automatically suggests excluding some of the irrelevant files. Excluding means filtering out; the files are not removed from disk.

Two new entities are created in the project's root directory: the .project file and the .dvt folder, which contains project-specific DVT configuration.

Building the Project

The auto-generated default build file contains a single build_auto_config directive, which tells DVT to scan the project and figure out what needs to be compiled. Once the build is done, the tool is ready to use.

Using Existing File Lists and Argument Files

If you already have some file lists or argument files that you passed to the simulator, you can simply reuse them in the build configuration file.

Command Line Interface

For a reusable, seamless integration of DVT into your flows, you should check out the DVT command line interface. It allows you to fully automate project creation and configuration, abstracting the whole process into a single command.