root/tags/lgt2305/integration/NOTES.txt

Revision 3849, 2.8 KB (checked in by pmoura, 16 months ago)

Improved documentation on the SWI-Prolog integration script.

  • Property svn:eol-style set to native
Line 
1================================================================
2Logtalk - Open source object-oriented logic programming language
3Release 2.30.5
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
26    yaplgt      YAP integration script
27
28On Windows systems, the Logtalk installer makes the Prolog integration
29shortcuts available from the "Start Menu/Programs/Logtalk" menu.
30
31The first run of the B-Prolog, Ciao, and XSB integration scripts must be
32made by an user with administrative rights (on POSIX systems, run them
33once as root or using sudo; in Windows systems run them once from an
34administrative account).
35
36The GNU Prolog integration script provides adequate performance for
37development. For production environments, improved performance can be
38achieved by generating a new GNU-Prolog top-level that includes Logtalk.
39
40The SWI-Prolog integration script assumes XPCE is installed. If that's
41not the case, comment out the loading of the file "xpcehook.pl" on the
42"integration/logtalk_swi.pl" file.
43
44Other Prolog compilers require manual steps for integration with Logtalk.
45See the "configs/NOTES.txt" file for details.
46
47The environment variables LOGTALKHOME and LOGTALKUSER should be defined
48in order to run the integration scripts (see the "INSTALL.txt" file for
49details on setting the variables).
50
51Note that the integration scripts and shortcuts may fail if you use non-
52standard locations for your Prolog compilers.
53
54Depending on the size and complexity of your Logtalk applications, you
55may need to change the integration scripts in order to allocate more
56memory to the back-end Prolog compilers. Please consult the documentation
57on the Prolog compilers you intend to use for details.
58
59All the scripts accept command-line options, which are passed straight to
60the back-end Prolog compiler. For example (on a POSIX operating-system,
61using SWI-Prolog as the back-end compiler):
62
63    % swilgt -g "write('Hello world!'), nl"
64
65However, keep in mind that the integration scripts already use the back-end
66Prolog command-line option that allows a initialization file to be loaded
67in order to bootstrap Logtalk. See the scripts/shortcut files for details.
Note: See TracBrowser for help on using the browser.