Important Installation Notes
Maude for Windows 2.6

Table of contents

1. Table of contents.
2. Description.
3. The Maude Development Tools.
4. Running different cygwin installations and other cygwin issues.
5. Required files.
6. Included files.
7. Installing Maude for Windows. Installation types.
8. Uninstalling Maude for Windows.
9. Modifying the cygwin.bat file.
10. Installing Cygwin a posteriori.
11. Credits.

Description.

This installer allows you to run Maude on a Windows platform without requiring any aditional software installed in your system. The maude binary included in the installer has been compiled with the help of the Cygwin environment.

This binary version should compatible with all the i586 compatible processors.

The Maude Development Tools.

The Maude Development Tools are a set of Eclipse plugins (publicly available under the terms of the GPL license) that provide:

• An API to use Maude from a Java Eclipse plug-in.
• A simple GUI to develop Maude programs inside the Eclipse platform, taking advantage of its features (friendly user interface, editors withsyntax highlighting, CVS/SVN features, etc.).

The Maude Development Tools plugin is designed to run in UNIX/Linux systems with the "bash" and "kill" commands. Because of Java does not provide native support for POSIX signals, we need these external programs to know the PID of the Maude process and to send the SIGINT signal to it (entering the debug mode).

This distribution of Maude for Windows is specially designed to be used by the Maude Development Tools Plug-in. It includes all the required files to execute these two commands in a Windows environment as if it were a UNIX/Linux system.

Running different cygwin installations and other cygwin issues.

The Cygwin team discourages running or even installing more than one Cygwin on the same OS instance of Windows. Cygwin is designed to be unique in your system (installed only in one place).

There are several situations that can produce errors or misconfigurations in your system, for example:

• Cygwin conflicts occur if cygwin discovers that there are more than one cygwin1.dll's on your machine. You should not have multiple versions of cygwin1.dll in your system. If you have them, they should not be in the search path (they must be isolated, and not loaded at the same time).
• Cygwin keeps its file system mount point information in the registry. This is global to any cygwin application.
• Cygwin maintains a uniqued shared memory region when a cygwin application is running, this can cause problem between different versions, ...
• etc.

If you have not installed Cygwin previosly to Maude for Windows, you will not have any problem running Maude. If you have Cygwin installed in your system, the installer will try to install Maude without interfering with Cygwin. Nevertheless, you should read this document If you experience problems running Maude for Windows, you shoul avoid to run any other Cygwin applications at the same time.

If you are unable to get the Maude for Windows application running, maybe you should try to compile Maude by yourself.

Required files.

To run Maude as an standalone program with the default options you will need:

• cygwin1.dll

To run Maude inside the Maude Development Tools plug-in, the programs "bash" and "kill" are also required. These programs need the following libraries:

• cygwin1.dll
• cygncurses-8.dll
• cygintl-3.dll
• cygiconv-2.dll
• cygreadline6.dll

Bash also needs the "/tmp" folder. In case you have not installed Maude previously, this folder will be missing. By selecting the option "MDT Eclipse plugin options -> Required mount points", the "cygwin\tmp" folder in the Maude for Windows installation directory will be mounted in "/tmp", avoiding the warning message.

Included files.

The maude files included are:

• maude.exe (Maude executable)
• maude.ico (Icon file)
• license.txt (GPL v2 license)
• prelude.maude (Maude interpreter standard prelude. v2.5)
• full-maude.maude (Full Maude specification. v 2.4)
• model-checker.maude (Maude LTL satisfiability solver and model checker. v2.3)
• linear.maude (Maude Diophantine solver. v2.3)
• socket.maude (Maude internet socket external objects. v2.3)
• term-order.maude (Strict total ordering on terms of a given kind. v2.3)
• machine-int.maude (Approximation of Maude 1.0 MachineInt. v2.3)
• metaInterpreter.maude (Maude meta-interpreters. v.2.5)
• readme_2.6.htm (This file).
• styles.css (CSS Stylesheet for the readme HTML document).

Cygwin is requierd to run Maude under Windows. To avoid to have to install Cygwin completely, the requierd files are included in this installation, these are:

• /bin/cygwin1.dll (Cygwin dll environment)
• /bin/cygncurses-8.dll (Required by bash.exe)
• /bin/cygintl-3.dll (Required by bash.exe)
• /bin/cygiconv-2.dll (Required by bash.exe)
• /bin/cygreadline6.dll (Required by bash.exe)
• /bin/ls.exe (Required by maude.exe to list files)
• /bin/bash.exe (Needed by the Maude Development Tools -MDT- plug-in)
• /bin/kill.exe (Needed by the Maude Development Tools -MDT- plug-in)

Installing Maude for Windows. Installation types.

The installer provides some predefined installation types based on your system configuration. If the options that you have selected can conflict with any previous Cygwin configuration, the installer will warn you before the installation process starts.

The installer also creates a backup of the registry key corresponding to the mount points defined by your previous cygwin installation ("HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\"). The file with this information is "backup\mountpoints.reg", in your Maude for Windows installation directory. So that, you can always recover the previous state of this key to its initial state.

Best for this system.

We recommend this installation. The installer automatically checks your systems configuration looking for a previous cygwin installation. It tries to install the maximum number of options that does not conflict with your cygwin configuration (if found).

• If you have not cygwin installed in your system, all the options will be selected.

• If you have cygwin installed in your system and you do not plan to use the MDT plug-ins, you can directly deselect the "MDT Eclipse plug-in options" component.

• If you have cygwin installed and you plan to use the MDT plug-ins, you can try any of the following two solutions:

  1. Install the required binary files provided by the installer and add them to the path environment variable. This option implies that you will have to modify the PATH environment variable in you "cygwin.bat" file by hand.
  2. Try to use the binary files provided by your previous cygwin installation. In this case, you will have to add manually your "/bin" (for example, by default it will be, "c:\cygwin\bin") folder to the PATH environment variable. This option may cause problems if you have different versions of the cygwin libraries in your system.

Full.

This installation type selects all the components without checking if they conflict with your system configuration. In that case, you will be warned.

Maude only.

This installation type selects the all the components required to run Maude, excluding the ones related with the MDT plug-ins. This install type should no conflict with any previous installation of cygwin.

Custom.

In case you select a set of components that does not correspond to any of the previous types, the Custom type will be selected.

Uninstalling Maude for Windows.

Maude for Windows provides an uninstallation program to remove all the installed components. When the program is executed, it scans the windows registry to find all the mount points defined in the cygwin environment. These mount points are showed in a list to the user, who can select which ones are going to be removed. By default, the mount points that are linked to folders under the MaudeFW program directory are selected to be deleted.

Modifying the cygwin.bat file.

To run properly the Maude Development Tools plug-in, the "bash.exe" and "kill.exe" commands must be on the search path of the system (the PATH environment variable). This step can be done automatically by the installation program if you select the "Add cygwin files to path" component. You can see the result in this example:

Microsoft Windows XP [Versión 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\>echo %PATH%
C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;
d:\Program Files\cvsnt;d:\Program Files\MaudeFW\cygwin\bin;

C:\>

Nevertheless, if you have a complete installation of Cygwin in your system, to include these files when installing Maude for Windows may cause problems when running Cygwin. To solve this, you only have to modify the "cygwin.bat" file, in the cygwin directory, modifying by hand its contents.

By default "cygwin.bat" will contain be something like this:

@echo off

c:
chdir c:\cygwin\bin

bash --login -i

Adding a line setting the value of the PATH var would solve the problem, for example:

@echo off

SET PATH=%SystemRoot%\system32;%SystemRoot%

c:
chdir c:\cygwin\bin

bash --login -i

Installing cygwin a posteriori.

If you have decided to install Cygwin once you have installed Maude for Windows, we recommend to uninstall Maude for Windows first (and its mount points). Then you can install Cygwin normally.

Finally, when the cygwin installation finishes, you can reinstall Maude for Windows, the installer will analyze your new configuration and will select the best options for your system.

Credits.

Maude is developed by the Maude Team at the University of Illinois at Urbana-Champaign.

The precompiled version of Maude for Windows is developed and maintained by Abel Gómez, member of The MOMENT Project, at the Universidad Politècnica de València.

The MOMENT Project members:

• Isidro Ramos Salavert.
• José Á. Carsí Cubel.
• Artur Boronat Moll.
• Abel Gómez Llana.

© Abel Gómez. 2011. The MOMENT project
http://moment.dsic.upv.es