Changes between Version 14 and Version 15 of BuildingTapWindows6


Ignore:
Timestamp:
12/15/16 12:23:35 (5 years ago)
Author:
Samuli Seppänen
Comment:

Minor clarifications to the build procedure

Legend:

Unmodified
Added
Removed
Modified
  • BuildingTapWindows6

    v14 v15  
    2828The actual build procedure is a bit convoluted:
    2929
    30 1. Run ''buildtap.py'' on the build computer, signing it with the SHA1 certificate. Make sure to include the correct cross-certificate and to timestamp the signature. Creating the installer (buildtap.py -p) does not make any sense right here.
     301. Run ''buildtap.py'' on the build computer, using the SHA1 certificate for signing. Make sure to include the correct cross-certificate and to timestamp the signature. Creating the installer (buildtap.py -p) does not make any sense right here.
    31311. Copy tap6.tar.gz to the signing computer
    32321. Unpack tap6.tar.gz on the signing computer
     
    35351. Copy the contents of the dual-signed tap6 directory to ''dist'' in tap-windows6 build root.
    36361. Run ''buildtap.py'' again using the same parameters as before, but ensure you do not ''clean'' (-c) or ''build'' (-b). You should only ''package'' (-p) the dist directory into an installer.
    37 1. Copy the installer to the code-signing computer, and append a signature to it using the EV SHA2 certificate. Right now, this process has not been automated, but the command-line is fairly easy to construct manually by looking at [https://github.com/mattock/sign-tap6/ Sign-Tap6.ps1].
     371. Copy the resulting ''installer'' to the code-signing computer, and append a signature to it using the EV SHA2 certificate. Right now, this process has not been automated, but the command-line is fairly easy to construct manually by looking at [https://github.com/mattock/sign-tap6/ Sign-Tap6.ps1].
    3838
    3939If this process sounds complicated, it's because it is. At some point would make sense to adapt buildtap.py to add both signatures automatically, which would simplify the process dramatically. However, that would require porting buildtap.py to Windows Kit 10, which would require a non-trivial amount of work.