diff options
| author | Simon Tatham <anakin@pobox.com> | 2015-12-12 09:17:33 +0000 |
|---|---|---|
| committer | Simon Tatham <anakin@pobox.com> | 2015-12-12 09:17:33 +0000 |
| commit | 0fa7baed1043089c390d80763ace267a681b69d3 (patch) | |
| tree | 465a6d8ec15dd0438f7024bc237edbd03f805bde | |
| parent | 7000b0c70a409afc427b3012d55366577dc0418e (diff) | |
| download | puzzles-0fa7baed1043089c390d80763ace267a681b69d3.zip puzzles-0fa7baed1043089c390d80763ace267a681b69d3.tar.gz puzzles-0fa7baed1043089c390d80763ace267a681b69d3.tar.bz2 puzzles-0fa7baed1043089c390d80763ace267a681b69d3.tar.xz | |
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.
| -rw-r--r-- | Buildscr | 7 |
1 files changed, 7 insertions, 0 deletions
@@ -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 |