| 1 | ================================================================= |
|---|
| 2 | Logtalk - Object oriented extension to Prolog |
|---|
| 3 | Release 2.17.1 |
|---|
| 4 | |
|---|
| 5 | Copyright (c) 1998-2004 Paulo Moura. All Rights Reserved. |
|---|
| 6 | ================================================================= |
|---|
| 7 | |
|---|
| 8 | |
|---|
| 9 | Installing Logtalk is just a matter of decompressing the downloaded |
|---|
| 10 | archive and copying the resulting directory to a suitable location. |
|---|
| 11 | The Logtalk directory can reside in any user accessible location. |
|---|
| 12 | This location depends on the working environment and on the number |
|---|
| 13 | of users. The "misc" sub-directory contains some shell scripts for |
|---|
| 14 | easy installation of Logtalk on Unix and Unix-like operating systems. |
|---|
| 15 | |
|---|
| 16 | |
|---|
| 17 | INSTALLING FOR A SINGLE USER |
|---|
| 18 | |
|---|
| 19 | In the case of a single user, the Logtalk directory can simply be |
|---|
| 20 | copied to the user home directory. |
|---|
| 21 | |
|---|
| 22 | |
|---|
| 23 | INSTALLING FOR MULTIPLE USERS |
|---|
| 24 | |
|---|
| 25 | In the case of multiple users, the Logtalk directory can be copied to |
|---|
| 26 | any location that its accessible by all the users. |
|---|
| 27 | |
|---|
| 28 | Regarding directory and file permissions, it is advisable to make all files |
|---|
| 29 | read-only in order to avoid user tempering. However, the library and examples |
|---|
| 30 | sub-directories (and possibly the compiler sub-directory, depending on the |
|---|
| 31 | chosen Prolog compiler) must be user writable as compiling Logtalk source |
|---|
| 32 | files generates intermediate Prolog files, which are written to the same |
|---|
| 33 | location as the source files. However, making directories world-writable is a |
|---|
| 34 | security risk. There are two alternatives. The first one is to pre-compile the |
|---|
| 35 | library and all examples and to turn on the compiler option "smart_compilation" |
|---|
| 36 | in order to avoid the need of recompilation when the files are loaded by the |
|---|
| 37 | users. The second alternative is to copy the Logtalk xml, examples, and library |
|---|
| 38 | directories to each user directory (the "misc" sub-directory contains a shell |
|---|
| 39 | script for automating these copies). |
|---|
| 40 | |
|---|
| 41 | |
|---|
| 42 | ENVIRONMENT VARIABLES |
|---|
| 43 | |
|---|
| 44 | In Unix and Unix-like systems is recommended that you define an environment |
|---|
| 45 | variable named $LOGTALKHOME pointing to the Logtalk installation for use with |
|---|
| 46 | your Prolog compilers. If you use a csh shell, add the following line to your |
|---|
| 47 | ~/.cshrc file: |
|---|
| 48 | |
|---|
| 49 | setenv LOGTALKHOME "/your/installation/directory/lgt2171" |
|---|
| 50 | |
|---|
| 51 | If you use a bash shell, add the following lines to your ~/.profile file: |
|---|
| 52 | |
|---|
| 53 | LOGTALKHOME="/your/installation/directory/lgt2171" |
|---|
| 54 | export LOGTALKHOME |
|---|
| 55 | |
|---|
| 56 | When using the provided shell script for installing Logtalk, a symbolic link |
|---|
| 57 | to the Logtalk installation directory is automatically created. The link is |
|---|
| 58 | named "logtalk". In this case, use this symbolic link to define the |
|---|
| 59 | environment variable in order to avoid breaking it when upgrading Logtalk. |
|---|