CADP (CONSTRUCTION AND ANALYSIS OF DISTRIBUTED PROCESSES)
WINDOWS INSTALLATION
This document is intended to every person planning to use CADP on a computer running a Microsoft operating system of the Windows family. If you do not plan to use CADP in a Windows environment, you can avoid reading this file.
SECTION 1. DEFINITIONS
In the sequel:
SECTION 2. INSTALLING A UNIX EMULATION
Before installing CADP on your Windows system, you have to enrich your Windows system with "Unix-like" extensions. The reason for this is the following.
All the CADP tools distributed in binary form for Windows (i.e., all files with extension ".exe", ".dll", or ".a" enclosed in the "bin.win32" directories of the CADP distribution) are pure Windows executables. However, some of these tools may invoke some Unix commands (e.g., "ls", "mv", "cp", etc. as well as a C compiler) which are not available on standard Windows systems.
Moreover, several CADP tools are written in Bourne shell language (e.g., all files enclosed in the "com" directories of the CADP distribution). The Bourne shell interpreter is available by default on Unix systems, but not on Windows systems.
For technical and economical reasons, we have chosen not to rewrite the CADP tools entirely, but rather to assume that CADP was to be run on a Windows enriched with "Unix-like" features, including a Bourne shell.
There are several Unix extensions for Windows available on the market. For the moment, we only support the Cygwin software distributed by RedHat (formerly, Cygnus Solutions) under the General Public License. See
for detailed information about Cygwin.The following explanations apply to Cygwin 1.5.25-7 (December 2007) and version 2.573.2.2 of the Cygwin Net Release Setup Program. We hope that they will still be valid for later versions of Cygwin. Please notify cadp@inria.fr if you notice changes in more recent releases Cygwin.
SECTION 3. REMOVING OBSOLETE VERSIONS OF CYGWIN
If you have already on your machine a version of Cygwin that works well with CADP, we recommend that you keep this existing version unchanged.
In a few cases however, we recommend that you remove your current version of Cygwin and install the most recent version available. This might be necessary if:
TO REMOVE CYGWIN 1.1.4 AND HIGHER
Simply remove the directories "/bin", "/etc", "/lib", "/sbin", "/tmp", "/usr", and "/var" (for instance, by dropping them into the trash can).
Do not remove the "/home" directory, which is supposed to contain your local files and settings.
TO REMOVE CYGWIN 1.1.2 (OLD VERSIONS)
Click on the "Start" button and select "Programs", then "Cygnus Solutions", and then run the corresponding "Uninstall" program that appears in the menu; if this program is not in the menu, locate the file "uninst.bat" and execute this file by double-clicking on its icon. Then, make sure that the Cygwin folders ("bin", "etc", "lib"...) have been removed; if not, delete them manually. Finally, it is necessary to clean the registry manually, as the "Uninstall" program does not do this properly. Click on the "Start" button, then select "Run". Type "regedit" in the command-line input and click on "OK". In the registry editor window, select "Edit", then "Find", type "cygwin" in the line input and click on "OK". If the editor finds a registry entry matching this string, delete this key by pressing <Delete> on your keyboard. Then, press <F3> on your keyboard to find the next registry entry matching "cygwin". Proceed repeatedly until you have removed all the registry keys related to the old version of Cygwin. Finally exit the registry editor by clicking "Registry", then "Exit".
TO REMOVE CYGWIN BETA-VERSION B20.1 (VERY OLD VERSIONS)
Click on the "Start" button, then select "Settings", then "Control Panel", then click on "Add/Remove Programs", then select "Cygwin ...", and finally "Add/Remove" to run the Uninstall program.
SECTION 4. INSTALLING CYGWIN
In general, Cygwin can be installed in any directory. However, if you want to use it with CADP, it must be installed directly in the root directory "C:\" assuming that Windows is also installed on drive "C:".
The reason for this is the following. The binary programs contained in the CADP distribution (e.g. caesar, bcg_io, etc.) are "pure" Win32 executables. They are not compiled against the Cygwin DLL, which allows them to be fully independent from Cygwin (so that other Unix emulations could be used in the future). For a proper functionning of "pure" Win32 executables and Cygwin executables, it is required that the root directory of Windows (i.e., "\") and the root directory of Cygwin (i.e., "/") coincide. Therefore, if you install Cygwin at a different place than "\" then Win32 program will not understand Cygwin pathnames (there exists a Cygwin command named "cygpath" for performing pathname conversions, but using this command would require to modify all the script-shells of CADP in a Cygwin-dependent way, which we have chosen to avoid).
Note: as far as we know, the approach that would consist in placing the Cygwin files and sub-directories into one single directory (e.g., "C:\cygwin") and creating links to these files and sub-directories does not work either. Cygwin supports symbolic links indeed, but they are not understood by Win32 applications. Conversely, the Windows shortcuts (files with ".lnk" extensions) are not recognized by Cygwin (shortcuts to directories are not even understood by the Windows command interpreter "cmd.exe").
C:\bin C:\etc C:\lib C:\sbin C:\srv C:\tmp C:\usr C:\var and the files
C:\cygwin.bat C:\cygwin.ico do not exist already, as the installation of Cygwin will overwrite them. Should they exist already, then you should move, rename, or remove them before installing Cygwin.
If the directory "C:\home" exists, it can be left unchanged, as the Cygwin installer will not overwrite it (hopefully).
Note: Remember that lower-case and upper-case letters are equivalent in Windows (but not always in Cygwin).
3) Create a NEW, EMPTY directory (say, C:\cygsetup).
4) Download the Cygwin installer file from
http://www.cygwin.com/setup.exe
or a backup copy (version 2.573.2.2) in
ftp://ftp.inrialpes.fr/pub/vasy/cadp/installator.win32/setup.exe
and save "setup.exe" in the empty directory C:\cygsetup.DO NOT EXECUTE directly "setup.exe" BEFORE saving it into an empty directory, otherwise it might pollute your current directory with lots of files.
5) Then, double-click on the icon of file C:\cygsetup\setup.exe. A window entitled "Cygwin Net Release Setup Program" opens.
Besides the above mandatory packages, you might wish to install some additional, optional packages. In particular, installing "Archive", "Editors", and "Utils" seems a reasonable idea.
Click on "Next"
SECTION 5. CONFIGURING CYGWIN
The current version of Cygwin is not sufficient for a proper functionning of the CADP tools.
The VASY team provides a shell-script named "cadp_cygwin.com" that modifies the Cygwin distribution to solve these problems. More information about the required modification can be obtained by reading the shell-script code.
Still logged on as the Administrator, download "cadp_cygwin.com" from
ftp://ftp.inrialpes.fr/pub/vasy/cadp/installator.win32/cadp_cygwin.com
and save it in "C:\cygsetup\cadp_cygwin.com".Do not execute "cadp_cygwin.com" as an ordinary Windows application, because it is a Unix shell-script. This would be useless.
Instead, open a Cygwin shell window either by clicking on the "Cygwin" icon freshly added on your desktop or by clicking on the "Start" button of Windows and selecting "Programs", then "Cygnus Solutions", then "Cygwin Bash Shell". This opens a black command-line window.
In this window, type the following command:
bash /cygsetup/cadp_cygwin.com
(type this command exactly as specified: do not replace "bash" with "sh")
In order to save disk space, the directory C:\cygsetup can be now removed safely as it only contains useless files
rm -rf /cygsetup
Close all your Cygwin windows, as the application of "cadp_cygwin.com" has no effect on windows already open: it will only have effects on the Cygwin windows that you will open afterwards.
The Cygwin environment is now ready to function with CADP.
SECTION 6. INSTALLING A POSTSCRIPT VIEWER
The BCG_DRAW tool requires a PostScript viewer in order to display the BCG graphs. We recommend the use of the Ghostscript/GSview software. For information about this software, please consult
and
http://www.cs.wisc.edu/~ghost/gsview
If you already have a working version of Ghostscript/GSview installed on your machine, we recommend that you keep it unchanged.
Otherwise, you have two options: installing an old, stable version that is known to work properly with CADP, or installing the most recent version. Note that recent versions of GSview prompt the user for software registration every time Gsview is invoked.
You must be logged on as the Administrator to install Ghostscript and GSview (otherwise the registry will not be updated properly).
FIRST OPTION: INSTALLING GHOSTSCRIPT 5.50 / GSVIEW 2.7
Download Ghostscript 5.50 and GSview 2.7 for Windows
(3,429,376 bytes) from
http://mirror.cs.wisc.edu/pub/mirrors/ghost/aladdin/gs550/gsv27550.exe
orftp://ftp.inrialpes.fr/pub/vasy/cadp/installator.win32/gsv27550.exe
Save this file anywhere on the disk and double-click on it. We recommend that you keep the default installation directory (otherwise, you will have to customize the environment variables $CADP_PS_VIEWER and $CADP_PS_INTERPRETER later).
When the installation is complete, you can remove "gsv27550.exe".
SECOND OPTION: INSTALLING GHOSTSCRIPT 8.7 / GSVIEW 4.9
Download Ghostscript 8.7 (32-bit version) for Windows from
http://mirror.cs.wisc.edu/pub/mirrors/ghost/GPL/gs870/gs870w32.exe
Save this file anywhere on the disk and double-click on it. We recommend that you keep the default installation directory (otherwise, you will have to customize the environment variable $CADP_PS_VIEWER later).
Download GSview 4.9 (32-bit version) for Windows from
http://mirror.cs.wisc.edu/pub/mirrors/ghost/ghostgum/gsv49w32.exe
Save this file anywhere on the disk and double-click on it. We recommend that you keep the default installation directory (otherwise, you will have to customize the environment variable $CADP_PS_INTERPRETER later).
When the installation is complete, you can remove "gs861w32.exe" and "gsv49w32.exe".
Download Ghostscript 8.7 (64-bit version) for Windows from
http://mirror.cs.wisc.edu/pub/mirrors/ghost/GPL/gs870/gs870w64.exe
Save this file anywhere on the disk and double-click on it. We recommend that you keep the default installation directory (otherwise, you will have to customize the environment variable $CADP_PS_VIEWER later).
Download 64-bits software GSview 4.9 for Windows from
http://mirror.cs.wisc.edu/pub/mirrors/ghost/ghostgum/gsv49w64.exe
Save this file anywhere on the disk and double-click on it. We recommend that you keep the default installation directory (otherwise, you will have to customize the environment variable $CADP_PS_INTERPRETER later).
When the installation is complete, you can remove "gsv49w64.exe" and "gsv49w64.exe".
SECTION 7. LOWER THE FIREWALL TO ALLOW FTP DOWNLOADS
By default, recent versions of Windows (e.g., Windows XP) are protected by a firewall that blocks certain Internet connections. It may also happen that your machine is protected by a third-party firewall (which usually comes as part of an antivirus suite).
The CADP Installation Assistant relies on the FTP protocol to download the CADP software from INRIA servers, and to upload prototype license files to INRIA servers. It is usually blocked by Windows firewall(s). In such case, the following error message will be emitted:
Error: error reading "sockXXX": connection reset by peer
To have CADP installed on your machine, it is necessary to lower the firewall protection temporarily. The easiest solution is to desactivate the firewall totally while installing CADP and reactivate it afterwards. A more involved solution is to tune the firewall to allow FTP downloads and uploads.
SECTION 8. CONTINUE THE INSTALLATION OF CADP
Now, you are ready to install the CADP software itself. Go back to the page:
http://cadp.inria.fr/installator/index.html#win32