Code-sign the Windows puzzle binaries and installer.

Where facilities exist, that is. Like the approach I took with PuTTY
yesterday, Buildscr will now run a code-signing script over the binary
if you specify one in the bob config, and otherwise should fall back
to just leaving that step out.

diff --git a/Buildscr b/Buildscr
index a009d601c8b5a1db2ed930f9c5f95d9f29e9c6ed..a1cfb7e3c12a7ffff8112f537d9a1d13a352d919 100644 (file)
--- a/Buildscr
+++ b/Buildscr
@@ -61,8 +61,15 @@ delegate windows
   # FIXME: Cygwin alternative?
   in puzzles do/win vcvars32 && nmake -f Makefile.vc clean
   in puzzles do/win vcvars32 && nmake -f Makefile.vc VER=-DVER=$(Version)
+  # Code-sign the binaries, if the local bob config provides a script
+  # to do so. We assume here that the script accepts an -i option to
+  # provide a 'more info' URL, and an optional -n option to provide a
+  # program name, and that it can take multiple .exe filename
+  # arguments and sign them all in place.
+  ifneq "$(winsigncode)" "" in puzzles do $(winsigncode) -i http://www.chiark.greenend.org.uk/~sgtatham/puzzles/ *.exe
   # Build installer.
   in puzzles do/win iscc puzzles.iss
+  ifneq "$(winsigncode)" "" in puzzles do $(winsigncode) -i http://www.chiark.greenend.org.uk/~sgtatham/puzzles/ -n "Simon Tatham's Portable Puzzle Collection Installer" Output/setup.exe
   return puzzles/puzzles.chm
   return puzzles/*.exe
   return puzzles/Output/setup.exe