Installation Guide » History » Version 32
Alexander Kamkin, 09/26/2011 04:54 PM
1 | 1 | Alexander Kamkin | h1. Installation Guide |
---|---|---|---|
2 | |||
3 | h2. Introduction |
||
4 | |||
5 | 26 | Alexander Kamkin | This document describes the steps should be followed to install "С++TESK Testing ToolKit":http://forge.ispras.ru/projects/cpptesk-toolkit (hereinafter C++TESK). In addition to C++TESK, "Icarus Verilog":http://iverilog.icarus.com and "VeriTool":http://forge.ispras.ru/projects/veritool (hereinafter Verilog tools) are recommended to be installed (they are used for generating C/C++ API for Verilog modules). |
6 | 11 | Alexander Kamkin | |
7 | Before installing the toolkit make sure that [[System Requirements]] are met. |
||
8 | 1 | Alexander Kamkin | |
9 | h2. Installation |
||
10 | |||
11 | 12 | Alexander Kamkin | To install C++TESK, pass the following steps: |
12 | 1 | Alexander Kamkin | |
13 | 19 | Alexander Kamkin | # Download the latest version of the C++TESK package (@cpptesk-toolkit-src-*.tar.gz@) from the "Files":http://forge.ispras.ru/projects/cpptesk-toolkit/files page. |
14 | 20 | Alexander Kamkin | # Unzip the downloaded archive: |
15 | 18 | Alexander Kamkin | <pre> |
16 | % tar xf cpptesk-toolkit-src-*.tar.gz |
||
17 | </pre> |
||
18 | 28 | Alexander Kamkin | # Run the @install.sh@ script as follows. |
19 | 29 | Alexander Kamkin | |
20 | 27 | Alexander Kamkin | * To install C++TESK without installing the Verilog tools, run: |
21 | 22 | Alexander Kamkin | <pre> |
22 | % install.sh |
||
23 | 1 | Alexander Kamkin | </pre> |
24 | 32 | Alexander Kamkin | * To install C++TESK together with the Verilog tools not reinstalling the Verilog tools (if they have been already installed), run: |
25 | 23 | Alexander Kamkin | <pre> |
26 | % install.sh --install-veritool |
||
27 | 31 | Alexander Kamkin | </pre> |
28 | 23 | Alexander Kamkin | * To install C++TESK and to (re)install Icarus Verilog and VeriTool: |
29 | 25 | Alexander Kamkin | <pre> |
30 | % install.sh --force-install-veritool |
||
31 | </pre>Icarus Verilog and VeriTool will be installed even if they have been installed already. |
||
32 | 1 | Alexander Kamkin | |
33 | 12 | Alexander Kamkin | Home directories for all of the tools are chosen according to the following rules: |
34 | 1 | Alexander Kamkin | |
35 | 12 | Alexander Kamkin | # 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. |
36 | # If the environment variable CPPTESK_HOME is not defined, it will be assigned to the value $ISPRAS_HOME/tools/cpptesk-toolkit. |
||
37 | # If the environment variable ICARUS_HOME is not defined, it will be assigned to the value $ISPRAS_HOME/tools/verilog. |
||
38 | # It the environment variable VERITOOL_HOME is not defined, it will be assigned to the value $ISPRAS_HOME/tools/veritool. |
||
39 | # C++TESK is installed into the folder $CPPTESK_HOME. |
||
40 | # Icarus Verilog (if it is required) is installed into the folder $ICARUS_HOME. |
||
41 | # VeriTool (if it is required) is installed into the folder $VERITOOL_HOME. |
||
42 | 6 | Alexander Kamkin | |
43 | h3. Manual installation of Icarus Verilog and VeriTool |
||
44 | |||
45 | 1 | Alexander Kamkin | 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. |
46 | 2 | Alexander Kamkin | |
47 | 7 | Alexander Kamkin | For manual installation of Icarus Verilog the following steps should be passed: |
48 | 1 | Alexander Kamkin | |
49 | 7 | Alexander Kamkin | # If the system variable $ICARUS_HOME is not set, it should be assigned. E.g., the following command sequence can help: |
50 | <pre> |
||
51 | 1 | Alexander Kamkin | export ICARUS_HOME=<path_for_Icarus_Verilog_installation> |
52 | echo "export ICARUS_HOME=$ICARUS_HOME" >> "$HOME/.profile" |
||
53 | echo "export ICARUS_HOME=$ICARUS_HOME" >> "$HOME/.bashrc" |
||
54 | 7 | Alexander Kamkin | </pre> |
55 | # It the folder $ICARUS_HOME does not exist, it should be created: |
||
56 | <pre> |
||
57 | 1 | Alexander Kamkin | mkdir -p "$ICARUS_HOME" |
58 | 7 | Alexander Kamkin | </pre> |
59 | # Having changed the directory to the one with installation package of Icarus Verilog, it is necessary to apply the following command sequence: |
||
60 | <pre> |
||
61 | 1 | Alexander Kamkin | tar xf verilog-0.9.4.tar.gz |
62 | cd verilog-0.9.4 |
||
63 | ./configure --prefix="$ICARUS_HOME" |
||
64 | make && make install |
||
65 | 7 | Alexander Kamkin | </pre> |
66 | 1 | Alexander Kamkin | |
67 | 7 | Alexander Kamkin | For manual installation of VeriTool the following steps should be passed: |
68 | 1 | Alexander Kamkin | |
69 | 9 | Alexander Kamkin | # If the system variable $VERITOOL_HOME is not set, it should be assigned. E.g., the following command sequence can help: |
70 | <pre> |
||
71 | 10 | Alexander Kamkin | export VERITOOL_HOME=< _path_for_VeriTool_installation_ > |
72 | 1 | Alexander Kamkin | echo "export VERITOOL_HOME=$VERITOOL_HOME">>"$HOME/.profile" |
73 | echo "export VERITOOL_HOME=$VERITOOL_HOME">>"$HOME/.bashrc" |
||
74 | 9 | Alexander Kamkin | </pre> |
75 | # It the folder $VERITOOL_HOME does not exist, it should be created: |
||
76 | <pre> |
||
77 | 1 | Alexander Kamkin | mkdir -p "$VERITOOL_HOME" |
78 | 9 | Alexander Kamkin | </pre> |
79 | # Having changed the directory to the one with installation package of VeriTool, it is necessary to apply the following command sequence: |
||
80 | <pre> |
||
81 | 1 | Alexander Kamkin | tar xf veritool-0.2.1-beta-20110702.tar.gz |
82 | cd veritool-0.2.1-beta-20110702 |
||
83 | ./configure --prefix="$VERITOOL_HOME" |
||
84 | make all && make install |
||
85 | 9 | Alexander Kamkin | </pre> |