Changeset 1730 for trunk/INSTALL

Show
Ignore:
Timestamp:
11/27/04 12:42:44 (4 years ago)
Author:
pmoura
Message:

Improved installation and configuration instructions.

Files:
1 modified

Legend:

Unmodified
Added
Removed
  • trunk/INSTALL

    r1718 r1730  
    2323 
    2424In the case of a single user, the Logtalk directory may simply be copied to  
    25 the user home directory. 
     25the user home directory. In alternative, assuming a user with administrative  
     26rights, the same setup described below for multiple users may be applied.  
     27This has the advantage of allowing the user to freely try and modify the  
     28provided examples, library, and configuration files with the option of, at  
     29any time, restoring the files to its original state by simply running one of  
     30the provided scripts. 
    2631 
    2732 
     
    3338feasible or desired). 
    3439 
    35 The "misc" sub-directory contains some shell scripts for easy installation  
    36 of Logtalk on Windows, Unix, and Unix-like operating systems (for details,  
     40The "misc" sub-directory contains shell scripts for easy installation of  
     41Logtalk on Windows, Unix, and Unix-like operating systems (for details,  
    3742see the misc/NOTES file). These scripts make all files read-only in order  
    3843to avoid user tempering. However, Logtalk directories such as "library"  
     
    4449world-writable is a security risk, one solution is to copy the directories  
    4550that need to be user-writable to each user home directory. The "misc" sub- 
    46 directory contains shell scripts (named cplgtdirs.*) which may be called  
    47 by the end-users for making such copies. 
     51directory contains shell scripts (named "cplgtdirs.*") which may be called  
     52by the end-users for making such copies. This is the preferred setup for a  
     53computer lab. When used with one of the Prolog compilers for which an  
     54integration script is provided on the "misc" directory, this setup allows  
     55end-users to independently customize default compilation options and  
     56library paths. 
    4857 
    4958 
     
    5665directory. The environment variable LOGTALKUSER should point to a directory  
    5766in your home directory where you want to store the user-specific Logtalk files 
    58 (for example, ~/logtalk). Both environment variables can be set for all users  
     67(for example, ~/logtalk). Both environment variables may be set for all users  
    5968by a user with administration privileges. The two environment variables can  
    6069have the same value if you are the only Logtalk user on your computer and if  
    61 you have full permissions to the Logtalk installation directory. 
    62  
    63 In addition, you may want to add the Logtalk sub-directory "xml", which  
    64 contains useful scripts for processing XML documenting files, to your  
    65 execution path. 
     70you have full permissions to the Logtalk installation directory. In addition,  
     71you may want to add the Logtalk sub-directory "xml", which contains useful  
     72scripts for processing XML documenting files, to your execution path. 
    6673 
    6774* Unix and Unix-like systems: 
     
    8794* Windows systems: 
    8895 
    89 In Windows 95/98/ME, environment variables are defined in the autoexec.bat  
     96In Windows 95/98/ME, environment variables are defined in the "autoexec.bat"  
    9097file (you will need to reboot after editing the file): 
    9198 
     
    104111paths can be declared using a dynamic predicate. This allows compiling and  
    105112loading of libraries and library files to be performed without worries about  
    106 library paths. In the compiler directory you will find some template files  
    107 which you can copy and edit to match your Logtalk installation and your Prolog  
    108 compiler and operating-system requirements. See the libpaths/NOTES file for  
     113library paths. In the "libpaths" directory you will find a sample file which  
     114you can copy and edit to match your Logtalk installation and your Prolog  
     115compiler and operating-system requirements. See the "libpaths/NOTES" file for  
    109116more details. 
    110117 
     
    113120 
    114121Logtalk interfaces with a specific Prolog compiler via a configuration file  
    115 that can be found on the $LOGTALKUSER/configs directory. These configuration  
     122that can be found on the "$LOGTALKUSER/configs" directory. These configuration  
    116123files can be customized by changing the values of the default flags and  
    117124compiler options which are used by Logtalk when compiling source files. For  
     
    121128"underscore_vars", "startup_message", "smart_compilation", and the set of  
    122129documentation-related flags ("xml", "xsl", "xmlspec", and "doctype"). Be sure  
    123 to read the $LOGTALKHOME/configs/NOTES file for Prolog specific notes; some  
     130to read the "$LOGTALKUSER/configs/NOTES" file for Prolog specific notes; some  
    124131Prolog compilers do not support the whole range of compilation flags.   
    125132 
     
    132139and the Logtalk compiler. The "misc" sub-directory contains several scripts  
    133140for automating the creation of these initialization files for some Prolog  
    134 compilers. In addition, be sure to read the configs/NOTES file notes on the  
     141compilers. In addition, be sure to read the "configs/NOTES" file notes on the  
    135142Prolog compilers that you intend to use.