hdt-1.0, hdt-2.0

How to avoid absolute (library) paths in your Sigasi Project files

Sigasi 2.21 introduced more default path variables. Read the first comment for more details.

In this blog post, I will describe how you can use path variables to avoid system dependent, absolute paths in your project files.

The default way to add a third party library (e.g. modelsim_lib) to your project is as follows:

  1. Add files to project
    • File > New > Folder
    • Advanced
    • Link to alternate location (Linked Folder)
    • Enter location.

Scripting Sigasi project creation

When you start using Sigasi, the first thing you have to do is set up a Sigasi project. This consists of two steps: (1) selecting the VHDL files that you want in your project and (2) configuring in which VHDL library these files must be mapped. In most cases you already have this information in one form or another.

Call for feedback: A new way to compile Sigasi/Eclipse project dependencies with an External Compiler

Sigasi allows you to split your design in multiple projects. This is an efficient way to deal with with big designs.

Duplicate std_logic_textio packages in VHDL 2008 projects

Duplicate ieee.std_logic_textio packageDuplicate ieee.std_logic_textio packageSince Sigasi 2.15, Sigasi detects duplicate (conflicting) design units. Duplicate design units are a bad idea because the compilation order determines which unit will eventually be used. This can lead to a lot of confusion and frustrating debugging sessions.

It turns out we also made this mistake.

Using VHDL2008 fixed point package in Sigasi

The IEEE VHDL 2008 fixed point package is currently not included in the Common Libraries of Sigasi (VHDL 2008) projects.