source: vis_dev/glu-2.1/README @ 7

Last change on this file since 7 was 6, checked in by cecile, 13 years ago

Ajout de glus pour dev VIS mod

File size: 6.2 KB
Line 
1This is release 2.1 of GLU, a set of BDD packages and low-level utilities.
2
3If you downloaded this to compile it with VIS, stop here -- see the README
4file in the VIS distribution for build and installation instructions.
5
6---------------------------------------------------------------------------
7To build GLU, you will need
8
9        * An ANSI C compiler (gcc will do, as will several versions of cc)
10        * GNU's make utility
11        * GNU's gzip utility
12        * Approximately 20 MB of free disk for the build
13        * Approximately 10 MB of free disk space for the installation
14
15---------------------------------------------------------------------------
16* Useful Addresses
17
18For the most recent version of GLU:
19        ftp://vlsi.colorado.edu/pub/vis/
20
21The VIS home page:
22        http://vlsi.colorado.edu/~vis/
23
24For the most recent version of the GNU tools:
25        http://www.gnu.org
26
27---------------------------------------------------------------------------
28This is the list of architecture/operating system/compiler
29combinations we have tested. (For installation with compilers marked
30with (*) please refer to the Platform Specific Instructions.)
31
32        * IBM RISC System/6000 / AIX Version 4.3.3 / gcc(*)
33        * Intel ix86 / Linux / gcc, g++, icc
34        * Intel ix86 / Windows XP with Cygwin 1.5.16-1 / gcc, g++(*)
35        * Intel ia64 / Linux / gcc
36        * Sun Sparc/ Solaris 2.8 / gcc, g++, cc(*)
37
38The following instructions are for the generic build process.  Before
39building the tool please refer to the section "* Platform Specific
40Instructions".
41
42---------------------------------------------------------------------------
43To build GLU for a single operating system:
44
45* Download the most recent versions of GLU from the address above
46
47* Move to where you would like the GLU source to reside and unpack
48  the distribution:
49
50        % cd /home/vis                                  # for example
51        % gzip -dc /tmp/glu-2.1.tar.gz | tar xf -
52
53* Move into the glu-2.1 directory and run configure, which will determine
54  some system-specific parameters and create the Makefile:
55
56        % cd glu-2.1
57        % ./configure
58
59  By default, this will use your system's native compiler.  To use gcc,
60 
61        % ./configure --enable-gcc
62
63  (You may wish to do this because you don't have the native compiler
64  installed or because it is not ANSI.)
65
66  Note: For some platforms where VIS is not supported for the native
67  compiler, the default compiler is set to gcc.
68
69  You can also compile glu with g++.  To do so,
70
71        % ./configure --enable-gcc=g++
72
73  Note: The Makefile by default uses the "-g" option for
74  compilation.  The resultant executables may be much larger than
75  those generated without using the "-g" option.  Using the
76  "-g" option however, provides debugging capabilities.
77
78  Note: The following is of interest only to people developing code
79  within vis.  For full debugging support, specify
80  --with-comp-mode=debug.  This will turn off optimization, and turn
81  on the assertions (sanity checks) in the code.  Similarly,
82  --with-comp-mode=purify and --with-comp-mode=quantify will link vis
83  with IBM Rational's Purify or Quantify tool.
84
85* Build the GLU system by running GNU's gmake utility:
86
87        % gmake
88
89  You may not have GNU make installed on your system under the name
90  'gmake' -- try make.  If this fails, you probably need the latest
91  version of GNU's make program -- download it from the address above.
92
93* (Optional) Test the build by invoking
94
95        % gmake check
96
97  This make take some time on slower machines.
98
99* Install the GLU library and its headers:
100
101        % gmake install                                 # optional
102
103  By default, this will put binaries, libraries, headers, and help files
104  in /usr/local/bin, /usr/local/lib, /usr/local/include, and /usr/local/share
105  respectively.  To choose a different location, provide a default prefix
106  when you invoke configure, e.g., to install in /projects/glu/bin, etc.,
107  use
108
109        % ./configure --prefix=/projects/glu
110
111  when configuring GLU.
112
113---------------------------------------------------------------------------
114To install GLU on multiple operating systems off the same source tree,
115see the file "INSTALL" in this directory.
116---------------------------------------------------------------------------
117
118* Platform Specific Instructions
119
120Note: some instructions apply to platforms we no longer support.
121
122** Little-endian machines:
123
124  vis-cal will occasionally fail when compiled with
125  --with-comp-mode=debug on little-endian machines like the Alphas and
126  the Intel ix86 CPUs.
127
128** DEC Alpha:
129
130  Warnings about MIN and MAX are harmless.
131  Warnings in the cuBdd package related to floating point are
132  also harmless.
133
134  The cc compiler will use 32-bit pointers by default.  To use 64-bit
135  pointers, invoke configure as follows:
136
137        % ./configure --enable-64
138
139  The gcc compiler will always use 64-bit pointers.
140
141** Solaris:
142
143  If Sun's C compiler is not installed on your system, use gcc
144  (./configure --enable-gcc).
145
146  Warnings about redefined symbol are harmless, so are the warnings that say
147  "end-of-loop code not reached".
148
149  The target check-cmu (which is executed as part of "make check")
150  fails with Solaris's native compiler unless -dalign is removed from
151  CFLAGS.  Although vis-cmu executes correctly even if compiled with
152  -dalign, if you plan to extensively use vis-cmu (especially develop
153  new code that uses MTBDDs) you should not compile with -dalign.
154
155  The sun cc compiler (Workshop 6 update 1) on ix86 appears to have a
156  bug in the optimization routines.  The -xO4 an -xO5 compiler options
157  will make vis crash.  As a safety precaution, we have changed the
158  optimization flag to be -xO3 for all Sun platforms that use the cc
159  compiler.  You can try higher optimization flags on your machine.
160  In general, it is hard to determine cc options that will give
161  optimal results on every platform, so it may pay off to play around
162  with the optimization options.
163
164** MS Windows with Cygwin:
165
166  You need Red Hat's Cygwin environment (freely available from
167  http://www.cygwin.com) to build GLU and VIS.
168
169  With Cygwin the configuration script automatically selects gcc.
170
171** AIX:
172
173  The configuration script automatically selects gcc.  The cal package
174  occasionally produces incorrect result if compiled with optimization
175  turned on.  If you plan to use the cal BDD package with AIX, you
176  should configure glu with --with-comp-mode=debug.
Note: See TracBrowser for help on using the repository browser.