Kerberos for Windows (KfW) 3.2.x Build Environment
Kerberos for Windows (KfW) is a specialized distribution of MIT Kerberos targeting the Windows platform. This document describes how to setup your KfW build environment.
Contents
Overview
The KfW build is automated by a set of Perl scripts and uses a combination of GNU and Microsoft tools to assemble the final build. In the following sections, we’ll outline the required components to run the build system.
Source Control Access
The Kerberos source tree is currently split over two source control systems. Current source is managed using Subversion (SVN), while legacy code is managed using the Concurrent Versioning System (CVS). The Cygwin distribution provides an SVN client that can be used with our Kerberized SVN repository.
Kerberized Access
Both source control systems support Kerberos authentication. In order to execute the KfW build script, you must use the Kerberos authentication mechanism as the script is not designed to prompt for passwords. Unfortunately, neither the CVS nor SVN client natively supports Kerberos authentication.
In order to provide Kerberized access for SVN, you must use a Kerberized SSH client in conjunction with the standard SVN client included with Cygwin. (In this guide, we will use a special build of PuTTY to accomplish this.)
In order to provide Kerberized access for CVS, we will use a custom build of the CVS client that supports Kerberos authentication.
Required Tools
The following tools are required to build KfW.
Scripting Support
As mentioned above, the Cygwin distribution is used to provide source control access clients. The distribution also provides several tools required by the KfW build script. These include sed, awk, cat, rm, and find. The script itself is written in Perl designed to be executed by ActiveState Perl.
Compilers and Libraries
The KfW build script requires the Microsoft Visual Studio build tools to assemble the KfW binaries. The Microsoft Platform SDK is required to provide the necessary libraries for the KfW build.
Documentation
External documentation is automatically generated by Doxygen as part of the build script.
Installation Packagers
The build script uses both the Windows Installer XML (WiX) toolset, as well as the Nullsoft Scriptable Install System (NSIS).
