root/tags/lgt2310/integration/NOTES.txt

Revision 3941, 2.9 KB (checked in by pmoura, 13 months ago)

Updated release number to 2.31.0 due to the incompatible changes in this version regarding compiler hooks.

  • Property svn:eol-style set to native
Line 
1================================================================
2Logtalk - Open source object-oriented logic programming language
3Release 2.31.0
4
5Copyright (c) 1998-2007 Paulo Moura.  All Rights Reserved.
6================================================================
7
8
9This directory contains Prolog integration shell scripts and auxiliary
10Prolog files.
11
12On POSIX systems, the Logtalk installers make the following integration
13scripts available from the command-line (you may need to adjust your
14system path):
15
16    bplgt       B-Prolog integration script
17    ciaolgt     Ciao Prolog integration script
18    cxlgt       CxProlog integration script
19    eclipselgt  ECLiPSe integration script
20    gplgt       GNU Prolog integration script
21    plclgt      K-Prolog integration script
22    qplgt       Qu-Prolog integration script
23    sicstuslgt  SICStus Prolog integration script
24    swilgt      SWI-Prolog integration script
25    xsblgt      XSB integration script (single-threaded)
26    xsbmtlgt    XSB integration script (multi-threaded)
27    yaplgt      YAP integration script
28
29On Windows systems, the Logtalk installer makes the Prolog integration
30shortcuts available from the "Start Menu/Programs/Logtalk" menu.
31
32The first run of the B-Prolog, Ciao, and XSB integration scripts must be
33made by an user with administrative rights (on POSIX systems, run them
34once as root or using sudo; in Windows systems run them once from an
35administrative account).
36
37The GNU Prolog integration script provides adequate performance for
38development. For production environments, improved performance may be
39achieved by generating a new GNU-Prolog top-level that includes Logtalk.
40
41The SWI-Prolog integration script assumes XPCE is installed. If that's
42not the case, comment out the loading of the file "xpcehook.pl" on the
43"integration/logtalk_swi.pl" file.
44
45Other Prolog compilers require manual steps for integration with Logtalk.
46See the "configs/NOTES.txt" file for details.
47
48The environment variables LOGTALKHOME and LOGTALKUSER should be defined
49in order to run the integration scripts (see the "INSTALL.txt" file for
50details on setting the variables).
51
52Note that the integration scripts and shortcuts may fail if you use non-
53standard locations for your Prolog compilers.
54
55Depending on the size and complexity of your Logtalk applications, you
56may need to change the integration scripts in order to allocate more
57memory to the back-end Prolog compilers. Please consult the documentation
58on the Prolog compilers you intend to use for details.
59
60All the scripts accept command-line options, which are passed straight to
61the back-end Prolog compiler. For example (on a POSIX operating-system,
62using SWI-Prolog as the back-end compiler):
63
64    % swilgt -g "write('Hello world!'), nl"
65
66However, keep in mind that the integration scripts already use the back-end
67Prolog command-line option that allows a initialization file to be loaded
68in order to bootstrap Logtalk. See the scripts files for details.
Note: See TracBrowser for help on using the browser.