[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gnugo-devel] How to build debugboard? / view.pike
From: |
Paul Pogonyshev |
Subject: |
Re: [gnugo-devel] How to build debugboard? / view.pike |
Date: |
Sat, 10 Jan 2004 23:54:19 +0000 |
User-agent: |
KMail/1.5.94 |
> > If you have Pike (http://pike.ida.liu.se/) scripting language installed
> > (or don't mind installing it), you cant try to use `view.pike' in
> > `regression/' directory instead. Unlike `debugboard' it is up to date
> > and works.
>
> view.pike is not included in the current 3.5.3 tarball - is that
> intentional?
Don't know whether it is intentional, but i do know how this happened.
Patch is below.
> I picked it out of CVS. Pike looks neat indeed - but I'm a bit
> afraid of learning yet another prog. language like C#, Java or Python :-)
> I'll give it a try though - aiming at learning more about GNU Go and
> comparing view.pike to the potential of the analyze-commands of GoGUI.
Well, you don't have to know Pike to use scripts written in it.
> Paul, please note that the following will not suffice as a patch
> to eliminate libdfa.a from the Makefile. Needn't the setting of
> debugboard_DEPENDENCIES be changed too?
>
> > --- Makefile.am.~1.4.~ 2002-11-06 13:05:43.000000000 +0000
> > +++ Makefile.am 2004-01-09 20:13:24.000000000 +0000
> > @@ -17,7 +17,6 @@ INCLUDES = \
> > LDADD = \
> > $(top_builddir)/engine/libengine.a \
> > $(top_builddir)/patterns/libpatterns.a \
> > - $(top_builddir)/patterns/libdfa.a \
> > $(top_builddir)/sgf/libsgf.a \
> > $(top_builddir)/utils/libutils.a
That's a patch for `Makefile.am'. Once Dan runs `automake' over it
and you will run `./configure' at your machine, the change will be
in `Makefile' in all places where it is needed. The point is that
`Makefile.am' is way shorter and simplier than `Makefile' itself. No
one prevents you from hacking your `Makefile' directly, though.
Paul
--- Makefile.am.~1.73.~ 2003-12-30 13:29:50.000000000 +0000
+++ Makefile.am 2004-01-10 23:54:03.000000000 +0000
@@ -24,7 +24,8 @@ TST = 13x13b.tst 13x13.tst arb.tst arend
noinst_SCRIPTS = eval.sh regress.sh test.sh eval3.sh
EXTRA_DIST = golois games $(TST) $(noinst_SCRIPTS) regress.awk \
- BREAKAGE regress.pl regress.plx regress.pike breakage2tst.py
+ BREAKAGE regress.pl regress.plx regress.pike breakage2tst.py \
+ view.pike
# Remove these files here... they are created locally
DISTCLEANFILES = *.orig *~
- [gnugo-devel] How to build debugboard?, aquarius, 2004/01/09
- Re: [gnugo-devel] How to build debugboard?, Arend Bayer, 2004/01/09
- Re: [gnugo-devel] How to build debugboard?, Paul Pogonyshev, 2004/01/09
- Re: [gnugo-devel] How to build debugboard? / view.pike, aquarius, 2004/01/09
- Re: [gnugo-devel] How to build debugboard? / view.pike,
Paul Pogonyshev <=
- Re: [gnugo-devel] How to build debugboard? / view.pike, bump, 2004/01/10
- Re: [gnugo-devel] How to build debugboard? / view.pike, bump, 2004/01/11
- Re: [gnugo-devel] How to build debugboard? / view.pike, Gunnar Farneback, 2004/01/11
- Re: [gnugo-devel] How to build debugboard? / view.pike, bump, 2004/01/11
- Re: [gnugo-devel] How to build debugboard? / view.pike, bump, 2004/01/12
- Re: [gnugo-devel] How to build debugboard? / view.pike, Gunnar Farneback, 2004/01/12
- Re: [gnugo-devel] How to build debugboard? / view.pike, bump, 2004/01/12