Changeset 1730 for trunk/INSTALL
- Timestamp:
- 11/27/04 12:42:44 (4 years ago)
- Files:
-
- 1 modified
-
trunk/INSTALL (modified) (9 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/INSTALL
r1718 r1730 23 23 24 24 In the case of a single user, the Logtalk directory may simply be copied to 25 the user home directory. 25 the user home directory. In alternative, assuming a user with administrative 26 rights, the same setup described below for multiple users may be applied. 27 This has the advantage of allowing the user to freely try and modify the 28 provided examples, library, and configuration files with the option of, at 29 any time, restoring the files to its original state by simply running one of 30 the provided scripts. 26 31 27 32 … … 33 38 feasible or desired). 34 39 35 The "misc" sub-directory contains s ome shell scripts for easy installation36 ofLogtalk on Windows, Unix, and Unix-like operating systems (for details,40 The "misc" sub-directory contains shell scripts for easy installation of 41 Logtalk on Windows, Unix, and Unix-like operating systems (for details, 37 42 see the misc/NOTES file). These scripts make all files read-only in order 38 43 to avoid user tempering. However, Logtalk directories such as "library" … … 44 49 world-writable is a security risk, one solution is to copy the directories 45 50 that 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. 51 directory contains shell scripts (named "cplgtdirs.*") which may be called 52 by the end-users for making such copies. This is the preferred setup for a 53 computer lab. When used with one of the Prolog compilers for which an 54 integration script is provided on the "misc" directory, this setup allows 55 end-users to independently customize default compilation options and 56 library paths. 48 57 49 58 … … 56 65 directory. The environment variable LOGTALKUSER should point to a directory 57 66 in your home directory where you want to store the user-specific Logtalk files 58 (for example, ~/logtalk). Both environment variables canbe set for all users67 (for example, ~/logtalk). Both environment variables may be set for all users 59 68 by a user with administration privileges. The two environment variables can 60 69 have 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. 70 you have full permissions to the Logtalk installation directory. In addition, 71 you may want to add the Logtalk sub-directory "xml", which contains useful 72 scripts for processing XML documenting files, to your execution path. 66 73 67 74 * Unix and Unix-like systems: … … 87 94 * Windows systems: 88 95 89 In Windows 95/98/ME, environment variables are defined in the autoexec.bat96 In Windows 95/98/ME, environment variables are defined in the "autoexec.bat" 90 97 file (you will need to reboot after editing the file): 91 98 … … 104 111 paths can be declared using a dynamic predicate. This allows compiling and 105 112 loading of libraries and library files to be performed without worries about 106 library paths. In the compiler directory you will find some template files107 whichyou can copy and edit to match your Logtalk installation and your Prolog108 compiler and operating-system requirements. See the libpaths/NOTESfile for113 library paths. In the "libpaths" directory you will find a sample file which 114 you can copy and edit to match your Logtalk installation and your Prolog 115 compiler and operating-system requirements. See the "libpaths/NOTES" file for 109 116 more details. 110 117 … … 113 120 114 121 Logtalk interfaces with a specific Prolog compiler via a configuration file 115 that can be found on the $LOGTALKUSER/configsdirectory. These configuration122 that can be found on the "$LOGTALKUSER/configs" directory. These configuration 116 123 files can be customized by changing the values of the default flags and 117 124 compiler options which are used by Logtalk when compiling source files. For … … 121 128 "underscore_vars", "startup_message", "smart_compilation", and the set of 122 129 documentation-related flags ("xml", "xsl", "xmlspec", and "doctype"). Be sure 123 to read the $LOGTALKHOME/configs/NOTESfile for Prolog specific notes; some130 to read the "$LOGTALKUSER/configs/NOTES" file for Prolog specific notes; some 124 131 Prolog compilers do not support the whole range of compilation flags. 125 132 … … 132 139 and the Logtalk compiler. The "misc" sub-directory contains several scripts 133 140 for automating the creation of these initialization files for some Prolog 134 compilers. In addition, be sure to read the configs/NOTESfile notes on the141 compilers. In addition, be sure to read the "configs/NOTES" file notes on the 135 142 Prolog compilers that you intend to use.
