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