From cf880225edb1b6a5cb27dec01ba54c61822788f2 Mon Sep 17 00:00:00 2001 From: Simon Tatham Date: Sat, 5 Aug 2006 17:20:29 +0000 Subject: I'm sick of repeatedly adding and removing local changes to Recipe when testing a new game, so here's a new architecture for the Recipe file. mkfiles.pl now supports several new features: - an `!include' directive, which accepts wildcards - += to append to an existing object group definition - the ability to divert output to an arbitrary file. So now each puzzle has a `.R' file containing a fragment of Recipe code describing that puzzle, and the central Recipe does `!include *.R' to construct the Makefiles. That way, I can keep as many experimental half-finished puzzles lying around my working directory as I like, and I won't have to keep reverting Recipe when I check in any other changes. As part of this change, list.c is no longer a version-controlled file; it's now constructed by mkfiles.pl, so that it too can take advantage of this mechanism. [originally from svn r6781] --- nullgame.R | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 nullgame.R (limited to 'nullgame.R') diff --git a/nullgame.R b/nullgame.R new file mode 100644 index 0000000..993f1ef --- /dev/null +++ b/nullgame.R @@ -0,0 +1,12 @@ +# -*- makefile -*- + +# The `nullgame' source file is a largely blank one, which contains +# all the correct function definitions to compile and link, but +# which defines the null game in which nothing is ever drawn and +# there are no valid moves. Its main purpose is to act as a +# template for writing new game definition source files. I include +# it in the Makefile because it will be worse than useless if it +# ever fails to compile, so it's important that it should actually +# be built on a regular basis. +nullgame : [X] GTK COMMON nullgame +nullgame : [G] WINDOWS COMMON nullgame -- cgit v1.1