Download

Latest version is 25.3.21 released on 25 November 2025

Kit distributions contain all our products:
  • DVT IDE for Eclipse and the DVT Debugger add-on
  • DVT IDE for VS Code / VSCodium
  • Verissimo SystemVerilog Linter
  • Specador Documentation Generator
For ease of deployment, the kit distributions include the selected Eclipse Platform, additional plugins for Eclipse, VSCodium and a compatible Java Runtime Environment.

DVT IDE can also be installed without a kit distribution as an Eclipse plugin or a VS Code extension.

Plugins pre-installed in all distros:

  • ANYEDIT (AnyEditTools)
  • CSV (org.fhsolution.eclipse.feature.csvedit)
  • EMACS (com.mulgasoft.emacsplus)
  • INDENT_GUIDE (net.certiv.tools.indentguide.feature) - Only in distros based on Eclipse >=4.11
  • TERMINAL (org.eclipse.tm.terminal)
  • VI (com.mbartl.eclipse.viplugin.feature)
  • XML (org.eclipse.wst.xml)

Plugins that you can manually enable using:

dvt_kit_installer.[sh|bat] install [list of plugins]

Revision Control System Plugins:

  • CVS (org.eclipse.cvs)
  • CLEARCASE (net.sourceforge.eclipseccase)
  • GIT (org.eclipse.egit)
  • PERFORCE.2021.2 (com.perforce.team.feature) - Only in distros based on Eclipse 4.22
  • PERFORCE.2022.1 (com.perforce.team.feature) - Only in distros based on Eclipse 4.22, 4.24
  • PERFORCE.2022.2 (com.perforce.team.feature) - Only in distros based on Eclipse 4.22, 4.24
  • PERFORCE.2023.1 (com.perforce.team.feature) - Only in distros based on Eclipse 4.22, 4.24
  • PERFORCE.2023.2 (com.perforce.team.feature) - Only in distros based on Eclipse 4.22, 4.24
  • PERFORCE.2024.1 (com.perforce.team.feature) - Only in distros based on Eclipse 4.33
  • SVN (org.eclipse.team.svn)

Language Support Plugins:

  • BASH (de.jcup.basheditor)
  • CPP (org.eclipse.cdt)
  • JAVA (org.eclipse.jdt)
  • JENKINSFILE (de.jcup.jenkinseditor) - Only in distros based on Eclipse 4.33
  • JSON (jsonedit-feature)
  • PERL (org.epic.feature.main)
  • PYTHON (org.python.pydev.feature)
  • RUBY (io.github.pyvesb.eclipse_solargraph)
  • TCL (org.eclipse.dltk.tcl)
  • YAML (de.jcup.yamleditor)

Review and Task Management Plugins:

  • GERRIT (org.eclipse.egerrit.feature)
  • MYLYN (org.eclipse.mylyn_feature)

Other Plugins:

  • EDITOR_CONFIG (editorconfig-eclipse-feature)

To replace the pre-installed ViPlugin with Vrapper you can run:

$DVT_HOME/bin/dvt_plugin_installer.sh    \
  -d com.mbartl.eclipse.viplugin.feature \
  -i net.sourceforge.vrapper             \
  -r http://vrapper.sourceforge.net/update-site/stable

To restore the pre-installed ViPlugin and remove Vrapper you can run:

$DVT_HOME/bin/dvt_plugin_installer.sh    \
  -d net.sourceforge.vrapper             \
  -i com.mbartl.eclipse.viplugin.feature \
  -r https://eda.amiq.com/update

The version of these plugins might be different across distros because it depends on the Eclipse version. To find out the exact version inside a distro run:

$DVT_HOME/bin/dvt_kit_installer.[sh|bat] help
Download version for with Eclipse
Size: N/A | SHA512: 1 / 2
Includes: Eclipse N/A, VSCodium N/A and Java Runtime Environment N/A
Eclipse Minimum requirements:
Recommended OS:
VSCodium Minimum requirements:
Recommended OS:
Download

Installing the kit distribution :
  • Open a terminal
  • Extract the kit distribution archive in a suitable location, referenced bellow as /path/to/dvt_eclipse
  • Set the DVT_HOME environment variable to point to /path/to/dvt_eclipse
         export DVT_HOME=/path/to/dvt_eclipse # sh / bash
         setenv DVT_HOME=/path/to/dvt_eclipse # csh / tcsh
  • Install additional plugins using $DVT_HOME/bin/dvt_kit_installer.sh

  • Open a terminal
  • Log in with the administrative user
  • Extract the kit distribution archive in a suitable location, referenced bellow as /path/to/dvt_eclipse
  • Set the DVT_HOME environment variable to point to /path/to/dvt_eclipse:
         export DVT_HOME=/path/to/dvt_eclipse # sh / bash
         setenv DVT_HOME=/path/to/dvt_eclipse # csh / tcsh
  • Install additional plugins using $DVT_HOME/bin/dvt_kit_installer.sh
  • IMPORTANT: Remove write permissions for other users using chmod -R go-w /path/to/dvt_eclipse

  • Open a terminal
  • Extract the kit distribution archive in a suitable location, referenced bellow as /path/to/dvt_eclipse
  • Set the DVT_HOME environment variable to point to /path/to/dvt_eclipse:
         export DVT_HOME=/path/to/dvt_eclipse # sh / bash
  • IMPORTANT: Remove the quarantine flag using sudo xattr -rd com.apple.quarantine $DVT_HOME
  • Install additional plugins using $DVT_HOME/bin/dvt_kit_installer.sh

  • Open a Command Prompt (not PowerShell)
  • Extract the kit distribution archive in a suitable location, referenced bellow as C:\path\to\dvt_eclipse
  • Set the DVT_HOME environment variable to point to C:\path\to\dvt_eclipse
         SET DVT_HOME=C:\path\to\dvt_eclipse
  • Install additional plugins using %DVT_HOME%\bin\dvt_kit_installer.bat

  • Open a Command Prompt as Administrator (not PowerShell)
  • Extract the kit distribution archive in a suitable location, referenced bellow as C:\path\to\dvt_eclipse
  • Set the DVT_HOME environment variable to point to C:\path\to\dvt_eclipse
         SET DVT_HOME=C:\path\to\dvt_eclipse
  • Install additional plugins using %DVT_HOME%\bin\dvt_kit_installer.bat
  • IMPORTANT: Remove write permissions for other users:
         Windows File Explorer → right click on C:\path\to\dvt_eclipse → Properties → Security.
         Depending on the installation location and the policies set by your company, this step might be different.

Setting the license:

The license must be passed to the application through one of the following environment variables:
DVT_LICENSE_FILE , DVTLMD_LICENSE_FILE or LM_LICENSE_FILE

Environment variables will be read in the order above and the first non-empty value will be used, the others will be ignored. Any variable containing only the string "FLEXLM" (case-insensitive) will be ignored.

Environment variables must be set before starting the application and the application must inherit the variables (e.g. when setting the variables in a terminal the application must be started from the same terminal).

The environment variables can be set:

  • In the shell startup or files .bashrc, .cshrc, .tcshrc, .zshrc
  • In the terminal used to start the application

In the DVT IDE for VS Code, the license can also be passed through the DVT.license.source setting accessible by using the Preferences: Open Settings command. Its value has precedence over license environment variables when DVT.environment.precedence is set to Settings environment variables .

The license environment variable or setting value must contain one or more FlexLM license sources.
Supported license sources are:

  • File-system path of a license file: /path/to/dvt.lic
  • License server address as port@host: 27001@licsrv
  • Three-server redundancy triad with comma ( , ) separated license servers: 27001@licsrv1,27001@licsrv2,30001@licsrv3
  • File-system path of a directory containing one or more license files with .lic extension: /path/to/licenses
  • Multiline string with the content of a license file surrounded by three curly brackets: {{{...}}}

Multiple license sources, with the exception of multiline string, can be specified by separating them with:

  • colon ( : ) on Linux/MacOS
  • ampersand ( & ) on any OS

The license must be passed to the application through one of the following environment variables:
DVT_LICENSE_FILE , DVTLMD_LICENSE_FILE or LM_LICENSE_FILE

Environment variables will be read in the order above and the first non-empty value will be used, the others will be ignored. Any variable containing only the string "FLEXLM" (case-insensitive) will be ignored.

Environment variables must be set before starting the application and the application must inherit the variables (e.g. when setting the variables in a terminal the application must be started from the same terminal).

The environment variables can be set:

  • Using Control Panel → System → Advanced system settings → Advanced tab → Environment variables
  • In the %USERPROFILE%\.dvt\env.bat script
  • In the %DVT_HOME%\bin\env.bat script
  • In the Command Prompt used to start the application

In the DVT IDE for VS Code, the license can also be passed through the DVT.license.source setting accessible by using the Preferences: Open Settings command. Its value has precedence over license environment variables when DVT.environment.precedence is set to Settings environment variables .

The license environment variable or setting value must contain one or more FlexLM license sources. Supported license sources are:

  • File-system path of a license file: C:\path\to\dvt.lic
  • License server address as port@host: 27001@licsrv
  • Three-server redundancy triad with comma ( , ) separated license servers: 27001@licsrv1,27001@licsrv2,30001@licsrv3
  • File-system path of a directory containing one or more license files with .lic extension: C:\path\to\licenses
  • Multiline string with the content of a license file surrounded by three curly brackets: {{{...}}}

Multiple license sources, with the exception of multiline string, can be specified by separating them with:

  • semicolon ( ; ) on Windows
  • ampersand ( & ) on any OS

Running:
  • DVT IDE for Eclipse: $DVT_HOME/bin/dvt.sh
  • DVT IDE for VS Code: $DVT_HOME/bin/dvt_code.sh
  • Verissimo: $DVT_HOME/bin/verissimo.sh
  • Specador: $DVT_HOME/bin/specador.sh

  • DVT IDE for Eclipse: $DVT_HOME\bin\dvt.bat
  • DVT IDE for VS Code: $DVT_HOME\bin\dvt_code.bat
  • Verissimo: $DVT_HOME\bin\verissimo.bat
  • Specador: $DVT_HOME\bin\specador.bat

Eclipse Update Site

DVT IDE for Eclipse can be installed in custom Eclipse installations using the following update sites:
  • Latest version: https://eda.amiq.com/update/latest
  • X.Y.Z version: https://eda.amiq.com/update/X.Y.Z
The archived update site can be downloaded from here:

VS Code VSIX

DVT IDE for Visual Studio Code can be installed from Visual Studio Marketplace using ext install amiq.dvt command or by downloading the platform independent extension and using the "Extensions: Install from VSIX" command in the Command Palette. The extension requires VS Code >= 1.97.2.

Frequently Asked Questions

How does VSCodium differ from VS Code?

Both products are built from the same MIT-licensed open-source codebase and share an almost identical set of features, with the main differences being:

VSCodium:

  • binary is released under an MIT open-source license
  • telemetry is completely removed from the build
  • uses Open VSX Registry as an extension marketplace
  • can't use Microsoft official integrations and proprietary extensions (GitHub Copilot, Remote-SSH, C++ for VS Code, ...), although some alternatives are available

VS Code:

  • binary is released under a proprietary license
  • telemetry is enabled (can be disabled in settings)
  • uses Visual Studio Marketplace as an extension marketplace
  • can use Microsoft official integrations and proprietary extensions such (GitHub Copilot, Remote-SSH, C++ for VS Code, ...)