logo_kerberos.gif

Difference between revisions of "Kerberos for Windows (KfW) Build Environment"

From K5Wiki
Jump to: navigation, search
(Kerberos for Windows (KfW) Build Environment moved to Kerberos for Windows (KfW) 3.2.x Build Environment: The build environment requirements will change for KfW 4.0)
 
 
(15 intermediate revisions by 4 users not shown)
Line 1: Line 1:
−
#REDIRECT [[Kerberos for Windows (KfW) 3.2.x Build Environment]]
 +
[[Category: Kerberos for Windows]]
  +
Directions for producing an environment in which to build
  +
Kerberos for Windows version 4.2
  +
  +
* Install 64-bit Windows 10.
  +
  +
* Install Visual Studio 2017 Community.
  +
** Check "Desktop development with C++".
  +
** Check "MFC and ATL support".
  +
** After installing, locate the Visual Studio 2017 menu under the start menu, and pin the x64 and x86 Native Tools Command Prompt entries to the task bar for e
  +
  +
* Install the chocolatey package manager from https://chocolatey.org/install (by pasting the PowerShell command line into an administrative powershell). Install the following packages:
  +
  +
choco install wixtoolset -y
  +
choco install strawberryperl -y
  +
choco install git -y -params '"/GitAndUnixToolsOnPath"'
  +
choco install emacs -y
  +
choco install windbg -y
  +
  +
* Add wix to the path.
  +
** search for System (control panel) and run it.
  +
** advanced system settings
  +
** environment variables (button at bottom)
  +
** click on wix, copy value.
  +
** click on path, click edit, click new, paste value and add "\bin".
  +
  +
Follow the instructions in src/windows/README to perform a build. NODEBUG can be set in the environment ("set NODEBUG=1") to avoid having to specify it on the nmake command line each time. For MIT-specific builds, also "set MIT_INTERNAL=1" or specify it on the nmake command line when building the installer.
  +
  +
Code signing:
  +
  +
signtool sign /v /d "MIT Kerberos for Windows installer" /a /fd sha256 /tr http://timestamp.comodoca.com /td sha256 foo.msi
  +
  +
See also https://support.comodo.com/index.php?/Default/Knowledgebase/Article/View/68/7/
  +
  +
More general KfW release engineering information at [[Kerberos for Windows Release Engineering]].

Latest revision as of 11:49, 7 April 2019

Directions for producing an environment in which to build Kerberos for Windows version 4.2

  • Install 64-bit Windows 10.
  • Install Visual Studio 2017 Community.
    • Check "Desktop development with C++".
    • Check "MFC and ATL support".
    • After installing, locate the Visual Studio 2017 menu under the start menu, and pin the x64 and x86 Native Tools Command Prompt entries to the task bar for e
  • Install the chocolatey package manager from https://chocolatey.org/install (by pasting the PowerShell command line into an administrative powershell). Install the following packages:
 choco install wixtoolset -y
 choco install strawberryperl -y
 choco install git -y -params '"/GitAndUnixToolsOnPath"'
 choco install emacs -y
 choco install windbg -y
  • Add wix to the path.
    • search for System (control panel) and run it.
    • advanced system settings
    • environment variables (button at bottom)
    • click on wix, copy value.
    • click on path, click edit, click new, paste value and add "\bin".

Follow the instructions in src/windows/README to perform a build. NODEBUG can be set in the environment ("set NODEBUG=1") to avoid having to specify it on the nmake command line each time. For MIT-specific builds, also "set MIT_INTERNAL=1" or specify it on the nmake command line when building the installer.

Code signing: 

   signtool sign /v /d "MIT Kerberos for Windows installer" /a /fd sha256 /tr http://timestamp.comodoca.com /td sha256 foo.msi

See also https://support.comodo.com/index.php?/Default/Knowledgebase/Article/View/68/7/

More general KfW release engineering information at Kerberos for Windows Release Engineering.

Retrieved from "https://k5wiki.kerberos.org./wiki?title=Kerberos_for_Windows_(KfW)_Build_Environment&oldid=5970"