root/trunk/QUICK_START.txt

Revision 4411, 5.2 kB (checked in by pmoura, 5 weeks ago)

Updated the release number to 2.33.0.

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
Line 
1================================================================
2Logtalk - Open source object-oriented logic programming language
3Release 2.33.0
4
5Copyright (c) 1998-2008 Paulo Moura.        All Rights Reserved.
6Logtalk is free software.  You can redistribute it and/or modify
7it under the terms of the "Artistic License 2.0" as published by
8The Perl Foundation. Consult the "LICENSE.txt" file for details.
9================================================================
10
11
12Quick start
13===========
14
15
16Starting up Logtalk
17-------------------
18
191. Install Logtalk by using either the installer provided for your
20operating-system (when available) or by following the instructions
21on the "INSTALL.txt" file. Depending on your operating-system, working
22environment, and favorite back-end Prolog compiler, you may already have
23a script or a shortcut installed for easily running Logtalk with your
24favorite Prolog compiler. In this case, skip the instructions below
25for starting up Logtalk and go straight to the instructions on running
26the examples.
27
28On POSIX operating-systems, the following shell scripts are installed
29by default for running Logtalk with selected back-end Prolog compilers
30(which must be up-to-date and properly installed for running the scripts!):
31
32* B-Prolog:       bplgt       (first run must use sudo)
33* CIAO:           ciaolgt     (first run must use sudo)
34* CxProlog:       cxlgt
35* ECLiPSe:        eclipselgt
36* GNU Prolog:     gplgt
37* K-Prolog:       plclgt
38* Qu-Prolog:      qplgt
39* SICStus Prolog: sicstuslgt
40* SWI-Prolog:     swilgt
41* XSB:            xsblgt      (first run must use sudo)
42* XSB MT:         xsbmtlgt    (first run must use sudo)
43* XSB MT 64 bits: xsbmt64lgt  (first run must use sudo)
44* YAP:            yaplgt
45
46On Windows systems, shortcuts for running Logtalk with selected back-end
47Prolog compilers are created on the "Start Menu/Programs/Logtalk" menu.
48If you get an unexpected failure when using one of the Prolog integration
49scripts, consult the "configs/NOTES.txt" file for compatibility notes.
50
512. Open the "manuals/index.html" file with a web browser.
52
533. Select the "Tutorial" link. This will provide you with a basic
54understanding of the main Logtalk concepts.
55
564. Go back to the "index.html" file, select the "User Manual" link,
57then the "Installing Logtalk" and "Running and debugging Logtalk
58programs" links. This will provide you with a basic understanding of
59how to start Logtalk as well as how to compile and load Logtalk code.
60
61
62In case a manual installation is necessary, and assuming that Logtalk
63supports your Prolog compiler, apply the following steps:
64
651. Read the "NOTES.txt" file in the "configs" sub-directory to check if
66any patch or workaround is needed for your compiler.
67
682. Start your Prolog compiler.
69
703. Change the current working directory of your Prolog session to the
71Logtalk installation directory. If you don't know which predicate to
72use, check the "configs/NOTES.txt" file or your Prolog compiler reference
73manual.
74
754. Compile and load the config file for your Prolog compiler.
76
775. Compile and load the Logtalk compiler/runtime found on the "compiler"
78sub-directory.
79
806. Adapt, if needed, the file "libpaths/libpaths.pl" to match your Logtalk
81installation, Prolog compiler, operating-system, and then compile and
82load it.
83
84Note that both the configuration files, the compiler/runtime files, and the
85library paths file are Prolog files. The predicate used to load these files
86depends on your Prolog compiler (consult your Prolog compiler documentation
87or take a look at the definition of the predicate '$lgt_load_prolog_code'/3
88in the config file. For most command-line compilers, you could type at the
89Prolog prompt something like:
90
91    | ?- ['configs/foo.config', 'compiler/logtalk.pl', 'libpaths/libpaths.pl'].
92
93Replace the file name "foo.config" with the appropriate config file name for
94your compiler.
95
96
97Running the examples
98--------------------
99
100You may now try some of the provided examples:
101
1021. Open the "examples" sub-directory. There you find several sub-directories
103with ready to run examples and a "NOTES.txt" file containing general
104instructions and a brief description of each example. Select and open one
105of the examples sub-directory.
106
1072. Read the example "NOTES.txt" file for a description of the example.
108
1093. Open the "SCRIPT.txt" file for instructions on how to load the example
110and for sample queries that you may try by copying-and-pasting them to
111your Prolog interpreter top-level.
112
113
114Writing your own programs
115_________________________
116
117Ready to start writing your own programs?
118
1191. Read the User Manual sections on "Programming in Logtalk" and "Running
120and debugging Logtalk programs".
121
1222. Take a look at the "wenv" sub-directory. There you will find syntax
123configuration files for popular text editors which enable syntax coloring
124and other text services when editing Logtalk source files.
125
1263. Create a sub-directory with a suitable name to hold all the files of
127your application. You may want to add the directory path to the "libpaths.pl"
128file mentioned above in order to easily load your application.
129
1304. Copy to this sub-directory a loader file from one of the example
131directories and modify it to load your own source files.
132
1335. Have fun!
Note: See TracBrowser for help on using the browser.