From 0fa7baed1043089c390d80763ace267a681b69d3 Mon Sep 17 00:00:00 2001 From: Simon Tatham Date: Sat, 12 Dec 2015 09:17:33 +0000 Subject: [PATCH] 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. --- Buildscr | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/Buildscr b/Buildscr index a009d60..a1cfb7e 100644 --- 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 -- 2.30.2