root/tags/lgt2180/INSTALL

Revision 1145, 3.2 KB (checked in by pmoura, 4 years ago)

Corrected typo.

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
Line 
1=================================================================
2Logtalk - Object oriented extension to Prolog
3Release 2.18.0
4
5Copyright (c) 1998-2004 Paulo Moura.  All Rights Reserved.
6=================================================================
7
8
9Installing Logtalk is just a matter of decompressing the downloaded
10archive and copying the resulting directory to a suitable location.
11The Logtalk directory can reside in any user accessible location.
12This location depends on the working environment and on the number
13of users. The "misc" sub-directory contains some shell scripts for
14easy installation of Logtalk on Unix and Unix-like operating systems.
15
16
17INSTALLING FOR A SINGLE USER
18
19In the case of a single user, the Logtalk directory can simply be
20copied to the user home directory.
21
22
23INSTALLING FOR MULTIPLE USERS
24
25In the case of multiple users, the Logtalk directory can be copied to
26any location that its accessible by all the users.
27
28Regarding directory and file permissions, it is advisable to make all files
29read-only in order to avoid user tempering. However, the library and examples
30sub-directories (and possibly the compiler sub-directory, depending on the
31chosen Prolog compiler) must be user writable as compiling Logtalk source
32files generates intermediate Prolog files, which are written to the same
33location as the source files. However, making directories world-writable is a
34security risk. There are two alternatives. The first one is to pre-compile the
35library and all examples and to turn on the compiler option "smart_compilation"
36in order to avoid the need of recompilation when the files are loaded by the
37users. The second, and probably best, alternative is to copy the Logtalk xml,
38examples, and library directories to each user home directory (the "misc"
39sub-directory contains a shell script for automating these copies).
40
41
42ENVIRONMENT VARIABLES
43
44In Unix and Unix-like systems is recommended that you define an environment
45variable named $LOGTALKHOME pointing to the Logtalk installation for use with
46your Prolog compilers. If you use a csh shell, add the following line to your
47~/.cshrc file:
48
49    setenv LOGTALKHOME "/your/installation/directory/lgt2180"
50
51If you use a bash shell, add the following lines to your ~/.profile file:
52
53    LOGTALKHOME="/your/installation/directory/lgt2180"
54    export LOGTALKHOME
55
56When using the provided shell script for installing Logtalk, a symbolic link
57to the Logtalk installation directory is automatically created. The link is
58named "logtalk". In this case, use this symbolic link to define the
59environment variable in order to avoid breaking it when upgrading Logtalk.
60
61
62CREATING NEW PROLOG TOP-LEVELS FOR AUTOMATIC LOADING OF LOGTALK
63
64Most Prolog compilers allows the user to define an initialization file that
65is automatically consulted at startup. This initialization file may contain
66directives for loading other files, such as the Logtalk configuration file
67and the Logtalk compiler. The "misc" sub-directory contains several shell
68scripts for automating the creation of these initialization files for some
69popular Prolog compilers. In addition, be sure to read the configs/NOTES file
70notes on the Prolog compilers that you intend to use.
Note: See TracBrowser for help on using the browser.