chess-gnuchess.el \
chess-ics.el \
chess-ics1.el \
+ chess-ics2.el \
chess-images.el \
chess-input.el \
chess-irc.el \
chess-scid.el \
chess-sjeng.el \
chess-sound.el \
+ chess-stockfish.el \
chess-test.el \
chess-transport.el \
chess-tutorial.el \
chess-ucb.el \
+ chess-uci.el \
chess-var.el \
chess-eco.el
-chess-auto.el: $(ELFILES) chess-auto.el.in
- cp -p $(srcdir)/chess-auto.el.in $@
- -rm $(top_builddir)/chess-auto.elc
- $(EMACS) --no-init-file --no-site-file -batch \
- -L $(top_builddir) -l chess-auto -f generate-autoloads \
+chess-auto.el: $(ELFILES)
+ echo ";;; DO NOT MODIFY THIS FILE" > $(top_builddir)/chess-auto.el
+ echo "(if (featurep 'chess-auto) (error \"Already loaded\"))" \
+ >> $(top_builddir)/chess-auto.el
+ $(EMACS) -batch -L $(srcdir) -l chess-maint.el \
+ -f chess-generate-autoloads \
$(top_builddir)/chess-auto.el $(srcdir)
+ echo "(provide 'chess-auto)" >> $(top_builddir)/chess-auto.el
+ ln -f $(top_builddir)/chess-auto.el $(top_builddir)/auto-autoloads.el
chess-eco.fen: chess-eco.pos chess-eco.el
$(EMACS) --no-init-file --no-site-file -batch \
-L $(srcdir) -l chess-eco -f chess-generate-fen-table \
chess-eco.pos chess-eco.fen
-TESTS = chess-test
+TESTS = chess-test
+DATABASE = $(shell test -r test/largedb.sg3 && echo test/largedb || echo test/historic.pgn)
+START = $(shell test -r test/largedb.sg3 && perl -e 'print int(rand(4000000)), "\n";' || echo 0)
+COUNT = 100000
-database = test/largedb
+# Note: There are 4,209,433 games in test/largedb, if you download the files
+# from:
+#
+# ftp://ftp.newartisans.com/pub/chess/largedb.7z
+#
+# If you have a dual-core CPU (or more), you'll get the best performance by
+# running a separate Emacs for each core. Here's how I run all the tests on
+# my dual-core MacBook Pro: (Note, removing chess-test is just a precaution,
+# since the Makefile will not regenerate it if you aborted a previous test
+# run).
+#
+# chess1 $ rm -f chess-test; nice -n 20 make START=0 COUNT=2104715 check
+# chess2 $ rm -f chess-test; nice -n 20 make START=2104715 COUNT=0 check
+#
+# I run both of these using `screen', with a vertical split so I can watch
+# them both running. I type C-a H in each screen window before starting, so
+# that all the output is logged to a file I can examine afterward.
+#
+# Note that these tests can take days to run. My MacBook Pro gets around
+# 2,000 plies per second. If you're a Lisp hacker and want to improve the
+# speed of that, the slowness is pretty much all in `chess-search-position',
+# in the file chess-pos.el.
-chess-test: Makefile
- echo "$(EMACS) -batch -L $(srcdir) -l chess-test.el -f chess-test '$(database)'" > $@
+chess-test:
+ echo "$(EMACS) -batch -L $(srcdir) -l chess-test.el -f chess-test '$(DATABASE)' $(START) $(COUNT); rm -f $(top_builddir)/chess-test" > $@
chmod u+x $@
+test/twic.pgn:
+ (set -e; f=$$(pwd)/$@; tmp_dir=`mktemp -d`; \
+ cd $$tmp_dir; \
+ lftp -c "open http://www.theweekinchess.com/zips/; mget twic*g.zip"; \
+ for zip in *.zip; do unzip $$zip; done; \
+ cat *.pgn > $$f; rm *.pgn)
+
+check-twic: test/twic.pgn
+ $(MAKE) DATABASE=$< START=0 COUNT=0 check
+
TAGS: $(dist_lisp_LISP)
@etags $(dist_lisp_LISP)
@echo TAGS rebuilt.