In order to make your migration from Sigasi HDT 1.0 to HDT 2.0 easier, this document outlines the main differences and improvements.

Type Time Compilation

Sigasi HDT 2.0 will compile your code as you type. No need to save your code, no need to run an external tool. While you type, Sigasi HDT 2.0 will update error and warning markers, code coloring and the outline.

Standard Libraries

The standard libraries (STD and IEEE) are now treated as regular libraries. The files are visible in your project explorer. The only difference is that we ship the standard files inside the tool: they are not visible on your disk and they are read-only.

Third Party Libraries

In Sigasi HDT 1.0 we had the concept of external libraries. This was a fix to speed up compilation of vendor libraries. We have completely dropped the concept of external libraries in favor of simplicity.

Project interdependencies

You can now organize reusable code (either your own, or third party libraries) in separate projects. For your new designs, you can import the packages and entities from those reusable projects.

Assigning Files to Libraries

The internal format for storing information about the VHDL libraries has changed. This information is now stored in the hidden file .library_mapping.xml.

Eclipse Internals

The internals have changed completely. In Eclipse speak, we have changed the builder and the project nature. No need to worry about these technical details. The only relevant consequence is that you cannot use Sigasi HDT 1.0 and HDT 2.0 on the same projects.

VHDL 93

At this time, we only support VHDL 93 in Sigasi HDT 2.0. We know this is a step back from what we offered in our older version. We will work on this in the near future.

Missing features

We are still busy porting the bulk of the HDT 1.0 features to Sigasi 2.0. Some of the things missing are: hierarchy view, some linter warnings, integration with simulators, complex refactorings, VHDL 2008. Read more about the missing features and our progress in porting them.