 |
Installation
Notes |
 |
This distribution was created and tested under both Windows NT and Windows
2000 Professional operating systems. Since the interface is ostensibly the
same (Win32) then there should be no major difficulty in porting to a Windows
98 or Windows 2000 User environment.
- The first step in installing a Sather implementation is to choose a
suitable location for the distribution files. Once this has been done
then the distribution should be unzipped (using, for example, the gzip
utility from Gnu) into the chosen directory.
- The next thing is to set up the environment variables needed by the
installation.
- The directory into which the distribution was unzipped should be
designated by the environment variable
SATHER_HOME.
- LOCALE - this should have a value composed of two
two-letter abbreviations separated by a Low Line character - '_'. The
first two letters should be the language of the local culture using
the abbreviation specified in ISO 639; the second pair defines the
territory as given in ISO 3166 (see here
for references).
During initial beta release the only one
available with the distribution is 'en_NZ'!
See also the documentation on the cultural compiler (lcc) for details of creating new cultural
descriptions when the full version of lcc becomes available.
- SATHER_ENV - this third environment variable should
be set to the value
<SATHER_HOME>/Resources/<LOCALE>/bin/LIBCHARS
It enables the low-level culture-dependent parameters to be read
from that file which is created during cultural description
compilation and moved to the appropriate directory.
- SATHER_RESOURCES - this environment variable is
optional unless a program which provides textual interaction with its
execution environment is being run. In that case additional
directories and message files will
need to be set up to contain the relevant message formatting strings.
This environment variable is expected to be a search path of
directories to be used when setting up the resources for the program
at execution time. This search path is normally expected to contain
the Resource directory used by the Required Library implementation
(see specifications)
-
<SATHER_HOME>/Resources/<LOCALE>
- Once these environment variables have been set up correctly and
checked then the execution serch path should be set up to include the
<SATHER_HOME>/Bin directory.
- It is normally wise at this stage to compile and run the Required
Library test suite (the source for which is the Sather module
test.module
in the directory
<SATHER_HOME>/Library/TestRequired. It would be wise to re-direct the
standard output channel to a test log file for later use if needed. The
standard error channel reports progress and indicates which test group
(for which class) failed. Note that this test runs with full
checking enabled and therefore carries out many millions of pre and post
condition checks, a significant number of which involve the comparison of
quite long (up to several hundred characters) strings.
Comments
or enquiries should be made to Keith
Hopper .
Page last modified: Tuesday, 16 May 2000.
|
 |