Windows Build Process

This page describes how the Windows build process operates and to run a build you must do so on a Windows Build machine. If you have not yet set one of these up, see [Windows Build Machine](Windows Build Machine) for details.

Getting Started

Having set up a build machine, everything is ready for you to perform a build. Within the git repository "openxt.git" is everything you need to compile all of the Windows components and package them. To get this process started check out openxt.git to any location on the build machine and navigate into the "windows" folder:

C:\Somewhere> git clone https://github.com/OpenXT/openxt.git
C:\Somewhere> cd openxt\windows

NOTE: DO NOT CLONE INTO A PATH CONTAINING SPACES THE BUILD WILL FAIL DUE TO XC-WINDOWS' RELIANCE ON THE WINDDK.

Contents of openxt/windows

Within this directory is everything that is required to drive the windows build:

• winbuild-all.ps1 - Actually does and manages the build
• winbuild-prepare.ps1 - prepares the system for a build
• configs directory - stores config files to dictate how the build operates
• BuildSupport directory - Additional scripts to be used as sub-steps of/support for the build
  And additional bits:
• mkbuildmachine directory - The scripts you used to [create your build machine](Windows Build Machine)

Running a build

To run a complete build, the script winbuild-prepare.ps1 must be used first to generate the config.xml file, followed by the winbuild-all.ps1 script.

C:\Somewhere\build-scripts\windows> powershell .\winbuild-prepare.ps1 config=<config-file> build=<build number> tag=<tag name> branch=<branch name> certname=<signing-certificate-name> developer=<true|false>
C:\Somewhere\build-scripts\windows> powershell .\winbuild-all.ps1

A typical developer prepare command would look like:

C:\Somewhere\build-scripts\windows> powershell .\winbuild-prepare.ps1 config=sample-config.xml build=123456 branch=master certname=developer developer=true

Where xen is the name of the certificate generated