-Write a section in print.py, if applicable.
-
-Add it to Recipe in _four_ places:
- - the `ALL' definition, to ensure it is compiled into the OS X binary
- - as a GTK build target
- - as a Windows build target
- - in the Unix `make install' section at the bottom.
-
-Add it to list.c so that the OS X binary will be able to select it
-from the menus.
+Create a .R file for it which:
+ - defines a Recipe symbol for it if it requires auxiliary object
+ files (make sure the general Recipe symbol doesn't contain the
+ icon)
+ - adds it to the `ALL' definition, to ensure it is compiled into
+ the OS X binary
+ - adds it as a GTK build target, with the optional GTK icon
+ - adds it as a Windows build target, with the optional resource
+ file
+ - adds auxiliary solver binaries if any
+ - adds it to $(GAMES) in the GTK makefile, for `make install'
+ - adds it to list.c for the OS X binary
+ - adds it to wingames.lst along with a textual name, for the build
+ system and Windows installer.
+
+If the puzzle is by a new author, modify the copyright notice in
+LICENCE and in puzzles.but. (Also in index.html, but that's listed
+below under website changes.)
+
+Double-check that the game structure name in the source file has
+been renamed from `nullgame', so that it'll work on OS X. Actually
+compiling it on OS X would be a good way to check this, if
+convenient.