![]() |
![]() |
![]() |
General Information
Tutorials
Reference Manuals
Libraries
Translation Tasks
Tools
Administration
![]() |
![]() |
Eli System Administration GuideInstalling EliEli is a collection of packages defining processes needed to build a translator from specifications. These processes are managed by an expert system called Odin. Odin is designed to manage complex software construction activities of any kind, and is therefore a stand-alone tool that is completely independent of Eli.
The Eli distribution contains a version of Odin that is capable of managing
the Eli software construction process.
That version of Odin will be built automatically when you run
As described in the distribution's `README' file, you can use Eli
from the distribution directory without further installation.
Because the distribution directory contains source code, however, it is
much larger than necessary to simply run Eli (see the end of the
distribution's `README' file for typical sizes).
Therefore we recommend that you run the
Running The installation process will result in the following files and directories being added to the directory in which Eli is installed (the `man', `bin', and `lib' sub-directories will be created by the installation process if they don't already exist):
These files and directories can be moved to other locations, provided that certain references are updated to reflect the change:
If you want to install Eli on multiple architectures, you will need a separate build for each. That means running through the configure-make cycle described in the configuration directory's `README' file for each architecture. Usually a multi-architecture installation has a distinct file system for multi-architecture software. That file system is managed in such a way that its name is the same on every architecture, but the actual storage referenced is architecture-specific. Your strategy for such a system is simple:
You will now be able to execute the command If you need a multi-architecture implementation, and space is at a premium, you can replace multiple copies of architecture-independent files by symbolic links to a single copy. Typically, about half of an installed Eli system can be shared. This implies, for example, that you can have three shared versions but only consume disk space equivalent to two separate versions. The `elilink' script in the `Eli' sub-directory of the distribution can be used to set up this sharing:
elilink working-directory master-directory
Master-directory is a directory containing an installed version of
Eli which is to be used as the complete master copy. It will be
unchanged by
`Elilink' calls itself recursively. This means that you will
either need to put the script in a directory that is on your
|