| User Manual: Installation |
|---|
| Web Polygraph |
Installation instructions have been synchronized with Polygraph version 2.0.0. See old user manual for earlier versions instructions.
Polygraph comes with an auto-configuration script. The script analyses your environment and adjusts Polygraph settings accordingly. The configuration step is required for Polygraph installation.
Unpack the archive. For example:
gunzip -c polygraph-2.0.0-src.tar.gz | tar -xvf -
Change your directory to polygraph/:
cd polygraph
Configure the distribution:
./configure
Watch configuration process for warnings or errors. In some cases, you may need to specify parameters for the configure script. Read the INSTALL file or type ./configure --help for more information.
Note that configuration process caches some of the results. The cache can be found in polygraph/config.cache. If you are fiddling with configuration parameters or are changing your setup, it is probably a good idea to remove that cache file before running configure again. Otherwise, the script may not notice the changes you have made. Furthermore, to remove all traces of a successful configuration and return to ground zero, you may run make distclean.
Change your directory to polygraph/ if you are not already there.
Run
gmake
If you do not have GNU make installed on your system, install it or try make. Native makers may work, but GNU maker is known to be more clever and robust. For example, many makers do not know how to deal with .cc files that Polygraph is using.
Watch out for compilation warnings and errors. Please report them to us. Not all warnings are harmful, but it never hurts to double check. In our environment, Polygraph compiles with no warnings.
Polygraph distribution consists of several optional programs that you may find useful. To create those programs, run
gmake all
Some of the optional tools may not build on your system. For example, polymon requires, among other things, properly installed ncurses library.
If you get errors during the build, please report them to us. At the very least, we can probably help you to fix the problem. In general, without your feedback, the bug will remain there -- we do not release source code that has compilation problems in our environment, so if you see an error, you can be pretty sure we do not know about it...
Polygraph is known to compile with g++, but other compilers may work as well.
At the time of writing, Polygraph does not ``install'' copies of executables and configuration files in a well-known shared directory such as /usr/local/polygraph/. Eventually, we will add installation code. Meanwhile, essential executables can be found in polygraph/src/.
rm -rf polygraph
This command will delete all files in the polygraph directory.