Installation Guide » History » Version 38
Alexander Kamkin, 09/26/2011 05:06 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 | 33 | 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 | 37 | Alexander Kamkin | * To install C++TESK and (re)install the Verilog tools, run: |
29 | 25 | Alexander Kamkin | <pre> |
30 | % install.sh --force-install-veritool |
||
31 | 34 | Alexander Kamkin | </pre> |
32 | 1 | Alexander Kamkin | |
33 | 34 | Alexander Kamkin | Home directories for the tools are chosen according to the following rules: |
34 | 1 | Alexander Kamkin | |
35 | 38 | Alexander Kamkin | # If the environment variable @$ISPRAS_HOME@ is not set, it will be assigned to the user’s home directory (usually, @/home/<user>@). |
36 | # If the environment variable @$CPPTESK_HOME@ is not set, it will be assigned to the value @$ISPRAS_HOME/tools/cpptesk-toolkit@. |
||
37 | # If the environment variable @$ICARUS_HOME@ is not set, it will be assigned to the value @$ISPRAS_HOME/tools/verilog@. |
||
38 | # It the environment variable @$VERITOOL_HOME@ is not set, it will be assigned to the value @$ISPRAS_HOME/tools/veritool@. |
||
39 | 35 | Alexander Kamkin | |
40 | 36 | Alexander Kamkin | C++TESK is installed into the folder @$CPPTESK_HOME@. |
41 | |||
42 | Icarus Verilog (if it is required) is installed into the folder @$ICARUS_HOME@. |
||
43 | |||
44 | VeriTool (if it is required) is installed into the folder @$VERITOOL_HOME@. |
||
45 | 6 | Alexander Kamkin | |
46 | h3. Manual installation of Icarus Verilog and VeriTool |
||
47 | |||
48 | 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. |
49 | 2 | Alexander Kamkin | |
50 | 7 | Alexander Kamkin | For manual installation of Icarus Verilog the following steps should be passed: |
51 | 1 | Alexander Kamkin | |
52 | 7 | Alexander Kamkin | # If the system variable $ICARUS_HOME is not set, it should be assigned. E.g., the following command sequence can help: |
53 | <pre> |
||
54 | 1 | Alexander Kamkin | export ICARUS_HOME=<path_for_Icarus_Verilog_installation> |
55 | echo "export ICARUS_HOME=$ICARUS_HOME" >> "$HOME/.profile" |
||
56 | echo "export ICARUS_HOME=$ICARUS_HOME" >> "$HOME/.bashrc" |
||
57 | 7 | Alexander Kamkin | </pre> |
58 | # It the folder $ICARUS_HOME does not exist, it should be created: |
||
59 | <pre> |
||
60 | 1 | Alexander Kamkin | mkdir -p "$ICARUS_HOME" |
61 | 7 | Alexander Kamkin | </pre> |
62 | # Having changed the directory to the one with installation package of Icarus Verilog, it is necessary to apply the following command sequence: |
||
63 | <pre> |
||
64 | 1 | Alexander Kamkin | tar xf verilog-0.9.4.tar.gz |
65 | cd verilog-0.9.4 |
||
66 | ./configure --prefix="$ICARUS_HOME" |
||
67 | make && make install |
||
68 | 7 | Alexander Kamkin | </pre> |
69 | 1 | Alexander Kamkin | |
70 | 7 | Alexander Kamkin | For manual installation of VeriTool the following steps should be passed: |
71 | 1 | Alexander Kamkin | |
72 | 9 | Alexander Kamkin | # If the system variable $VERITOOL_HOME is not set, it should be assigned. E.g., the following command sequence can help: |
73 | <pre> |
||
74 | 10 | Alexander Kamkin | export VERITOOL_HOME=< _path_for_VeriTool_installation_ > |
75 | 1 | Alexander Kamkin | echo "export VERITOOL_HOME=$VERITOOL_HOME">>"$HOME/.profile" |
76 | echo "export VERITOOL_HOME=$VERITOOL_HOME">>"$HOME/.bashrc" |
||
77 | 9 | Alexander Kamkin | </pre> |
78 | # It the folder $VERITOOL_HOME does not exist, it should be created: |
||
79 | <pre> |
||
80 | 1 | Alexander Kamkin | mkdir -p "$VERITOOL_HOME" |
81 | 9 | Alexander Kamkin | </pre> |
82 | # Having changed the directory to the one with installation package of VeriTool, it is necessary to apply the following command sequence: |
||
83 | <pre> |
||
84 | 1 | Alexander Kamkin | tar xf veritool-0.2.1-beta-20110702.tar.gz |
85 | cd veritool-0.2.1-beta-20110702 |
||
86 | ./configure --prefix="$VERITOOL_HOME" |
||
87 | make all && make install |
||
88 | 9 | Alexander Kamkin | </pre> |