source: vis_dev/vl2mv-2.3/README @ 104

Last change on this file since 104 was 18, checked in by cecile, 13 years ago

vl2mv added

File size: 3.7 KB
Line 
1This is release 2.3 of VL2MV, a system for translating high-level verilog
2desciption to BLIF-MV (a multi-valued extension of BLIF). BLIF-MV is the input
3format used by VIS/SIS, an integrated verification/synthesis system.
4For more information on VL2MV and BLIF-MV
5visit http://vlsi.colorado.edu/~vis/usrDoc.html
6
7---------------------------------------------------------------------------
8This is the list of architecture/operating system/compiler
9combinations we have tested.
10
11     * Intel ia32/x86_64 / Linux / gcc
12     * Intel ia32 / Windows XP/Vista with Cygwin 1.5 / gcc
13
14The following combinations are no longer supported, but should still
15work.
16
17     * Sun Sparc / Solaris 5.8 / gcc, cc
18     * Intel i386 / Solaris 5.8 / gcc, cc
19
20The following instructions are for the generic build process. 
21
22---------------------------------------------------------------------------
23Before compiling VL2MV, you will have to build GLU, a set of BDD packages and
24low-level utilities. You may obtain GLU from the Univeristy of Colorado VLSI
25lab at http://vlsi.colorado.edu/~vis/.
26
27To build GLU for a single operating System refer the GLU Readme file -
28http://vlsi.colorado.edu/~vis/Readme/README.glu
29
30Make sure that the GLU version is same as that of the VL2MV you are
31building  - after you unzip and untar the glu-version#.tar.gz, you
32will have a  directory named glu-version#. If the version # does not
33match the version number of the VL2MV you are trying to build, then
34move the directory to the version number that you require.
35
36eg. if you have glu-2.2 directory and you are building vl2mv-2.3
37(VL2MV version 2.3), then move glu-2.2 to glu-2.3
38
39> mv glu-2.2/ glu-2.3
40
41Also make sure that the variable VERSION in the Makefile.in under glu-version#/
42directory is set to that of the VL2MV package being installed (In the above
43example, you should set VERSION = 2.3 in the Makefle.in)
44
45Now compile and build (and install) GLU. You are now ready to build VL2MV.
46
471. Download the verion of VL2MV to the directory say <WORK_AREA>. You should
48have downloaded and unpacked GLU at <WORK_AREA> too.
49
502. Unpack VL2MV. Let's say the tar ball you downloaded is vl2mv-2.3.tar.gz
51
52> gunzip vl2mv-2.3.tar.gz
53This will create a vl2mv-2.3.tar file. Untar it using
54> tar -xvf vl2mv-2.3.tar
55This creates a directory named vl2mv-2.3/
56
57You can use
58> gunzip vl2mv-2.3.tar.gz | tar -xvf
59or
60> tar -xvzf vl2mv-2.3.tar.gz
61to do the same as mentioned before.
62
633. Move into the vl2mv-2.3 directory thus produced and execute the configure
64script which will create the Makefile after determining some of the system
65specific parameters.
66
67> cd vl2mv-2.3
68> ./configure
69
70By default, this will use your system's native compiler (cc). If you do not
71have cc or if you wish to use gcc instead, use
72
73> ./configure --enable-gcc
74
75Read the configure file for more options ( users developing code for vl2mv
76or vis may want to take a look ). Do not worry if some of the checks
77of the configure return "no." Concentrate on the warnings (if any) that the
78configure script produces.
79
80Now a Makefile and configure.status file are created.
81
824. Build the vl2mv system by
83
84> make
85
86Sometimes, the build may stop and ask you to excute config.status. Do that by
87
88> ./config.status
89
90This will create a new Makefile and you will have to start the build process
91again by typing "make" at the command promt.
92
93If the compilation goes through without any seg faults, you will find the
94vl2mv binary under <WORK_AREA>/vl2mv-2.3/
95
96If you want to install, remove the binary created or run any self-tests that
97come alongwith the package, use
98> make install
99> make clean
100> make check
101
102Read INSTALL file under <WORK_AREA>/vl2mv-2.3/ for install instructions.
103For more options, read Makefile file created by running configure script
104as explained under step 3.
Note: See TracBrowser for help on using the repository browser.