Difference between revisions of "Installation guidelines"

From The Maude System
Jump to: navigation, search
(Created page with "<small>(If you use [http://www.xemacs.org/ XEmacs], then you might find the Maude mode for XEmacs written by [http://www.iam.unibe.ch/~kai/ Kai Br...")
 
Line 1: Line 1:
<small>(If you use [http://www.xemacs.org/ XEmacs], then you might find the [[Media:Maude-mode.tar.gz|Maude mode]] for XEmacs
+
As explained in [[Maude Download and Installation|Maude's download page]], Maude has a single executable that can be allocated anywhere in you machine. However, there are several things you must take into account:
written by [http://www.iam.unibe.ch/~kai/ Kai Br&uuml;nnler] or  
+
 
the [[Media:Maude-mode2.el.zip|Maude mode]] written by Ellef Gjelstad useful.  
+
- Most Linux distributions allow the installation of Maude through their package management systems. It is not always updated though. To download the latest version of Maude you can get the zipped file from its [[official distribution site|http://maude.cs.illinois.edu/w/index.php/The_Maude_System]].
Extract the mode using the command "gunzip -c maude-mode.tar.gz | tar -xvf -" and follow instructions in maude-mode/README. Note that the Maude mode does not run under GNU Emacs. If you are using Emacs 24 please consider to use the [https://github.com/ssaavedra/maude-mode maude-mode] written by Santiago Saavedra. Please see the README for details.  
+
 
There are also language packages for Atom, Visual Studio Code, and other editors.</small>
+
- In a Linux/MacOS installation, you can unzip the distribution file anywhere in you disk. You can then add the folder in which it is located to your PATH environment variable, or create an alias or soft link in your /usr/local/bin/ folder. You choose.
 +
 
 +
- The compressed file distributed in Maude's official site includes, in addition to the executable files (for Linux and MacOS), several text files with Maude specifications. Maude tries to load one of them at start up, the prelude.maude file. The Maude interpreter checks for it in several directories, in the following order:
 +
 
 +
  1. the directories specified in the MAUDE_LIB environment variable,
 +
  2. the directory containing the executable, and
 +
  3. the current directory.
 +
 
 +
  And it is not only the prelude.maude file, the interpreter will follow this strategy when trying lo load any file. Therefore, it might be a good idea to include the path to the prelude.maude file in the MAUDE_LIB environment variable to be sure that it will always be found.
 +
 
 +
Maude's manual includes information on how to run Maude and how to load simple specifications (see [[Chapter 2|https://maude.lcc.uma.es/maude321-manual-html/maude-manualch2.html#x13-240002.2]]).
 +
 
 +
The Maude interpreter is all you need to run Maude programs. It is a command line tool, with no graphical user interface. You can write your specs directly in the terminal, but it is more convenient to use some editor to create them and then load them in the interpreter. Maude packages are available for more common text editors (Emacs, Visual Studio Code, Atom, Sublime, ...), check on your favorite editor's package management tool for it.
 +
 
 +
If you are a Windows user, our recommendation is to use [[WSL|https://docs.microsoft.com/en-us/windows/wsl/]]. After installing it, you can use Maude from the terminal or invoking it from some tool. For instance, some users like to use Atom facilities for invoking Maude directly from Atom.

Revision as of 19:46, 11 July 2022

As explained in Maude's download page, Maude has a single executable that can be allocated anywhere in you machine. However, there are several things you must take into account:

- Most Linux distributions allow the installation of Maude through their package management systems. It is not always updated though. To download the latest version of Maude you can get the zipped file from its http://maude.cs.illinois.edu/w/index.php/The_Maude_System.

- In a Linux/MacOS installation, you can unzip the distribution file anywhere in you disk. You can then add the folder in which it is located to your PATH environment variable, or create an alias or soft link in your /usr/local/bin/ folder. You choose.

- The compressed file distributed in Maude's official site includes, in addition to the executable files (for Linux and MacOS), several text files with Maude specifications. Maude tries to load one of them at start up, the prelude.maude file. The Maude interpreter checks for it in several directories, in the following order:

 1. the directories specified in the MAUDE_LIB environment variable,
 2. the directory containing the executable, and
 3. the current directory.
 And it is not only the prelude.maude file, the interpreter will follow this strategy when trying lo load any file. Therefore, it might be a good idea to include the path to the prelude.maude file in the MAUDE_LIB environment variable to be sure that it will always be found.

Maude's manual includes information on how to run Maude and how to load simple specifications (see https://maude.lcc.uma.es/maude321-manual-html/maude-manualch2.html#x13-240002.2).

The Maude interpreter is all you need to run Maude programs. It is a command line tool, with no graphical user interface. You can write your specs directly in the terminal, but it is more convenient to use some editor to create them and then load them in the interpreter. Maude packages are available for more common text editors (Emacs, Visual Studio Code, Atom, Sublime, ...), check on your favorite editor's package management tool for it.

If you are a Windows user, our recommendation is to use https://docs.microsoft.com/en-us/windows/wsl/. After installing it, you can use Maude from the terminal or invoking it from some tool. For instance, some users like to use Atom facilities for invoking Maude directly from Atom.