Project

General

Profile

Actions

Installation Guide » History » Revision 33

« Previous | Revision 33/74 (diff) | Next »
Alexander Kamkin, 09/26/2011 04:55 PM


Installation Guide

Introduction

This document describes the steps should be followed to install С++TESK Testing ToolKit (hereinafter C++TESK). In addition to C++TESK, Icarus Verilog and VeriTool (hereinafter Verilog tools) are recommended to be installed (they are used for generating C/C++ API for Verilog modules).

Before installing the toolkit make sure that System Requirements are met.

Installation

To install C++TESK, pass the following steps:

  1. Download the latest version of the C++TESK package (cpptesk-toolkit-src-*.tar.gz) from the Files page.
  2. Unzip the downloaded archive:
    % tar xf cpptesk-toolkit-src-*.tar.gz
    
  3. Run the install.sh script as follows.
  • To install C++TESK without installing the Verilog tools, run:
    % install.sh
    
  • To install C++TESK together with the Verilog tools not reinstalling the Verilog tools if they have been already installed, run:
    % install.sh --install-veritool
    
  • To install C++TESK and to (re)install Icarus Verilog and VeriTool:
    % install.sh --force-install-veritool
    
    Icarus Verilog and VeriTool will be installed even if they have been installed already.

Home directories for all of the tools are chosen according to the following rules:

  1. If the environment variable ISPRAS_HOME is not defined, it will be assigned to the address of the installing C++TESK user’s the home folder.
  2. If the environment variable CPPTESK_HOME is not defined, it will be assigned to the value $ISPRAS_HOME/tools/cpptesk-toolkit.
  3. If the environment variable ICARUS_HOME is not defined, it will be assigned to the value $ISPRAS_HOME/tools/verilog.
  4. It the environment variable VERITOOL_HOME is not defined, it will be assigned to the value $ISPRAS_HOME/tools/veritool.
  5. C++TESK is installed into the folder $CPPTESK_HOME.
  6. Icarus Verilog (if it is required) is installed into the folder $ICARUS_HOME.
  7. VeriTool (if it is required) is installed into the folder $VERITOOL_HOME.

Manual installation of Icarus Verilog and VeriTool

If the computer is not connected to the Internet, manual installation of Icarus Verilog and VeriTool is required. Installation packages can be downloaded using the following addresses: http://sourceforge.net/projects/iverilog/files/iverilog/0.9.4/verilog-0.9.4.tar.gz and http://forge.ispras.ru/projects/veritool/files.

For manual installation of Icarus Verilog the following steps should be passed:

  1. If the system variable $ICARUS_HOME is not set, it should be assigned. E.g., the following command sequence can help:
    export ICARUS_HOME=<path_for_Icarus_Verilog_installation>
    echo "export ICARUS_HOME=$ICARUS_HOME" >> "$HOME/.profile" 
    echo "export ICARUS_HOME=$ICARUS_HOME" >> "$HOME/.bashrc" 
    
  2. It the folder $ICARUS_HOME does not exist, it should be created:
    mkdir -p "$ICARUS_HOME" 
    
  3. Having changed the directory to the one with installation package of Icarus Verilog, it is necessary to apply the following command sequence:
    tar xf verilog-0.9.4.tar.gz
    cd verilog-0.9.4
    ./configure --prefix="$ICARUS_HOME" 
    make && make install
    

For manual installation of VeriTool the following steps should be passed:

  1. If the system variable $VERITOOL_HOME is not set, it should be assigned. E.g., the following command sequence can help:
    export VERITOOL_HOME=< _path_for_VeriTool_installation_ >
    echo "export VERITOOL_HOME=$VERITOOL_HOME">>"$HOME/.profile" 
    echo "export VERITOOL_HOME=$VERITOOL_HOME">>"$HOME/.bashrc" 
    
  2. It the folder $VERITOOL_HOME does not exist, it should be created:
    mkdir -p "$VERITOOL_HOME" 
    
  3. Having changed the directory to the one with installation package of VeriTool, it is necessary to apply the following command sequence:
    tar xf veritool-0.2.1-beta-20110702.tar.gz
    cd veritool-0.2.1-beta-20110702
    ./configure --prefix="$VERITOOL_HOME" 
    make all && make install
    

Updated by Alexander Kamkin about 13 years ago · 74 revisions