Changes between Version 41 and Version 42 of BuildingTapWindows6


Ignore:
Timestamp:
04/17/19 08:21:22 (3 years ago)
Author:
Samuli Seppänen
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BuildingTapWindows6

    v41 v42  
    9898}}}
    9999
    100 The EV dongle will probably prompt you twice per architecture (x86, x64, arm64) as it signs the catalog file and tapinstall.exe for each. Note that the -Force switch ''is required'' or the file hashes in the .cat files will be incorrect and the driver will not install.
     100If tap-windows6 build directory is shared via SMB you will get warnings about running scripts from the Internet. Unfortunately it is not possible to make this problem go away, even with the [https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/unblock-file?view=powershell-6 Unblock-File] CmdLet when working with SMB shares, unless you modify the global Powershell execution policy with [https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.security/set-executionpolicy Set-ExecutionPolicy] CmdLet.
     101
     102Once you're past the script warnings the EV dongle will probably prompt you twice per architecture (x86, x64, arm64) as it signs the catalog file and tapinstall.exe for each. Note that the -Force switch ''is required'' or the file hashes in the .cat files will be incorrect and the driver will not install.
    101103
    102104'''On build computer'''
     
    107109$ cd tap-windows6
    108110$ python.exe buildtap.py -p --ti=Windows-driver-samples\setup\devcon
     111$ cd sign-tap6
     112$ .\Sign-File -SourceFile ..\<installer-file>
    109113}}}
    110114