Hello!

System: WindowsXP SP2, intel 915DW chipset, Intel Celeron 2,5GHz

GNU prolog 1.3.0
GNU Prolog Win32 auto-install setup
[http://www.gprolog.org/setup-gprolog-1.3.0-mingw.exe]


1. In the chapter 3.2.1 "3.2.1  Starting/exiting the interactive
interpreter" of the buil-in help system of gprolog interpreter
Example with using gprolog did not work because of gprolog under windows
requers two "--" instead of one "-" and double " instead single '.


Existense text is:
Here is an example of using execution goal options: 
% gprolog -init-goal 'write(before), nl' -entry-goal 'write(inside), nl'
-query-goal 'append([a,b],[c,d],X)'

For Windows systems it mast be like this:
Here is an example of using execution goal options: 
gprolog --init-goal "write(before), nl" --entry-goal "write(inside), nl"
--query-goal "append([a,b],[c,d],X)"


2. In the directory ExamplesPL from GNU prolog 1.3.0 for Windows there are
NO ANY SUBDIRECTORY and following text from \ExamplesPL\readme may be not
refferred to Windows:
"
Each sub-directorie (YAP, WAMCC, SICSTUS, CIAO, BINPROLOG, XSB, SWI)
contains
3 files:

        MAKE_PROGS: a shell-script building the benchmarks
        MAKE_CLEAN: a shell-script removing build benchmarks
        HOOK.pl: the hook file needed for the corresponding system

To compile the benchmarks with a given system use MAKE_PROGS in the
associated directory (e.g. YAP):

        cd YAP
        MAKE_PROGS   (or MAKE_PROGS BENCH_NAME...)

MAKE_PROGS build the list of benchmarks passed as argument. In none, it
builds all benchmarks described in the file ../PROGS.  Be sure to be in the
sub-directory (cd) before doing MAKE_PROGS."


The first-time users of GNU Prolog & MinGW under Windows can not understand
from this readme how to compile examples, with what program they can use
makefile and so on.





Best regards, 
Alexander Trubitsyn
JSC "NCC", Russia
System Administrator

work  +7 (8312) - 150000 (715)
mobile  +7 951 9060011




_______________________________________________
Bug-prolog mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-prolog

Reply via email to