root/tags/lgt2214/INSTALL

Revision 1646, 3.8 KB (checked in by pmoura, 4 years ago)

Updated release number to 2.21.4.

  • 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.21.4
4
5Copyright (c) 1998-2004 Paulo Moura.  All Rights Reserved.
6=================================================================
7
8
9Installing Logtalk is just a matter of decompressing the downloaded archive
10and copying the resulting directory to a suitable location.
11
12The Logtalk directory can reside in any user accessible location.
13This location depends on the working environment and on the number of users.
14The "misc" sub-directory contains some shell scripts for easy installation
15of Logtalk on Windows, Unix, and Unix-like operating systems (for details,
16see the misc/NOTES file).
17
18
19INSTALLING FOR A SINGLE USER
20
21In the case of a single user, the Logtalk directory may simply be copied to
22the user home directory.
23
24
25INSTALLING FOR MULTIPLE USERS
26
27In the case of multiple users, the Logtalk directory can be copied to any
28location that its accessible by all the users (assuming that copying the
29Logtalk directory to each user home directory is not feasible or desired).
30
31Regarding directory and file permissions, it is advisable to make all files
32read-only in order to avoid user tempering. However, the library and examples
33sub-directories (and possibly the compiler sub-directory, depending on the
34chosen Prolog compiler) must be user writable as compiling Logtalk source
35files generates intermediate Prolog files, which are written to the same
36location as the source files. However, making directories world-writable is a
37security risk. One solution is to copy the Logtalk xml, examples, and library
38directories to each user home directory (the "misc" sub-directory contains
39some scripts which may be called by the end-users for making these copies).
40
41
42ENVIRONMENT VARIABLES
43
44It is recommended that you define an environment variable named LOGTALKHOME
45pointing to the Logtalk installation directory for use with your Prolog
46compilers. In addition, you may want to add the Logtalk sub-directory "xml",
47which contains useful scripts for processing XML documenting files, to your
48execution path.
49
50* Unix and Unix-like systems:
51
52If you use a csh shell, add the following line to your ~/.cshrc file:
53
54    setenv LOGTALKHOME /your/installation/directory/lgt2214
55    setenv PATH $PATH:$LOGTALKHOME/xml:$LOGTALKHOME/misc
56
57If you use a bash shell, add the following lines to your ~/.profile file:
58
59    LOGTALKHOME=/your/installation/directory/lgt2214
60    export LOGTALKHOME
61    PATH=$PATH:$LOGTALKHOME/xml:$LOGTALKHOME/misc
62    export PATH
63
64When using the provided shell script for installing Logtalk, a symbolic link
65to the Logtalk installation directory is automatically created. The link is
66named "logtalk". In this case, you may use this symbolic link to define the
67environment variable in order to avoid breaking it when upgrading Logtalk.
68
69* Windows systems:
70
71In Windows 95/98/ME, environment variables are defined in the autoexec.bat
72file (you will need to reboot after editing the file):
73
74    SET LOGTALKHOME=C:\your\installation\folder\
75
76In Windows NT/2000/XP, environment variables are defined using the System
77properties control panel (if you are a system administrator, you should use
78the JScript install script provided in the "misc" sub-directory).
79
80
81CREATING NEW PROLOG TOP-LEVELS FOR AUTOMATIC LOADING OF LOGTALK
82
83Most Prolog compilers allows the user to define an initialization file that
84is automatically consulted at startup. This initialization file may contain
85directives for loading other files, such as the Logtalk configuration file
86and the Logtalk compiler. The "misc" sub-directory contains several scripts
87for automating the creation of these initialization files for some Prolog
88compilers. In addition, be sure to read the configs/NOTES file notes on the
89Prolog compilers that you intend to use.
Note: See TracBrowser for help on using the browser.