Introduction

Assumed - you are running Windows Vista or Windows 7, and have Visual Studio 2010 (or the equivalent SDK and NMake) installed.

Get the Source

There are two options.

• Download the latest Veracity tarball.

or

• Clone the public repository: http://public.veracity-scm.com/repos/veracity. (Note that you won't be able to push to this repository.)

Unpack or checkout it the directory of your choice - for brevity, we'll pretend you put it under %USERPROFILE%\v, and so your source tree begins at %USERPROFILE%\v\veracity

Install Prerequisites

Install CMake

Grab cmake 2.8.3 or later from cmake.org.

Install CMake, making sure to add cmake to the PATH variable when prompted.

Install Cygwin

Cygwin is used to run a script that builds Veracity's third-party dependencies. That is the only thing it is used for, so it is possible to build and run Veracity without installing cygwin, but you will need to build the third-party dependencies by hand instead of using the script to do it for you. It's a long process, but you can just read throught the script and and do what it would do.

Visit cygwin.com, grab and run the setup utility from there. In addition to the stock Cygwin tools, you'll also need:

• patch (under Utils)
• unzip (under Archive)
• curl (under Net)

Add cygwin to PATH

C:\cygwin\bin needs to be in your path for building the third-party libraries and for running the test suite. You can add it temporarily in a command prompt, e.g.

PATH=%PATH%;C:\cygwin\bin

or add it permanently to your Windows user's path.

Create a Veracity Build Directory

You must open a Command Prompt that has the correct Visual Studio environment variables set. Go to the the Windows Start menu and select "Microsoft Visual Studio 2010" -> "Visual Studio Tools" -> "Visual Studio Command Prompt (2010)" (Or, to build them as 64-bit, choose "Visual Studio x64 Win64 Command Prompt (2010)").

From that command prompt, cmake will create a Visual Studio solution or NMake Makefiles for you. You just need to give it a place to work. For example, let's create a neighbor of our source directory.

mkdir %USERPROFILE%\v\debug

Then, to create a Visual Studio 2010 solution:

cd %USERPROFILE%\v\debug
cmake -G "Visual Studio 10" ..\veracity

Or, to create a solution for a 64-bit build:

cd %USERPROFILE%\v\debug
cmake -G "Visual Studio 10 Win64" ..\veracity

To use NMake instead, run:

cd %USERPROFILE%\v\debug
cmake -G "NMake Makefiles" ..\veracity

Add vv-thirdparty bin to PATH

The first time you perform cmake -G, the script will also download and build third party libraries Veracity needs, in %USERPROFILE%\v\vv-thirdparty, which takes a few minutes. As long as you keep your build trees in this folder, such that the build script can locate vv-thirdparty, this will only happen once.

Once vv-thirdparty is created, you'll need to add the binary directory to PATH:

set PATH=%PATH%;%USERPROFILE%\v\vv-thirdparty\x86\bin

or for 64bit builds

set PATH=%PATH%;%USERPROFILE%\v\vv-thirdparty\amd64\bin

Build Veracity

You now have a build tree, replete with Makefiles or Project files.

For Visual Studio users, simply open the solution, %USERPROFILE%\v\debug\veracity.sln, and build. Note that although the solution will contain both "Debug" and "Release" configurations, only "Debug" will build properly. To build "Release", you'll need to have CMake generate a separate release build tree. See the answer to this question for more detail.

For NMake users,

cd %USERPROFILE%\v\debug
nmake

Run the Test Suite

Only builds that have passed the test suite on all of SourceGear's in-house build machines are ever published. To run the test suite for yourself:

cd %USERPROFILE%\v\debug
ctest

All tests should pass. If there are failures, you can consult the logs.

Install Veracity

The Command Line Applications

To "install" veracity on your computer, update your PATH again, this time to include the Veracity command line tools, vv and vscript.

For Visual Studio Project users, add these to your PATH:

%USERPROFILE%\v\debug\src\cmd\Debug
%USERPROFILE%\v\debug\src\script\Debug

For NMake users, add these:

%USERPROFILE%\v\debug\src\cmd
%USERPROFILE%\v\debug\src\script

Enable the server (and bug tracking)

In order to enable Veracity's scrum bug tracking module or to run a veracity server you will also need to have a config setting called "server/files" pointed at a certain location. Run:

vv config set server/files "%USERPROFILE%\v\veracity\src\server_files"

The Tortoise Client

Important: For Tortoise, Debug and Release builds make a very big difference. Only Release builds will be loaded by Windows Explorer. Debug builds will only be loaded by Windows Explorer if there is a debugger attached to the explorer process. This is done to prevent a long-lived process from loading the dll, which would prevent the dll from being overwritten on a build.

If you want to try the Veracity Tortoise Client, which allows you to perform Veracity operations directly from Windows Explorer, you'll need to run one of the following commands from an administrator (elevated) command prompt:

If you used Visual Studio for the build, run this command:

regsvr32.exe %USERPROFILE%\v\debug\src\tortoise\VeracityShellExtension\Release\VeracityTortoise.dll

If your build was an NMake build:

regsvr32.exe %USERPROFILE%\v\debug\src\tortoise\VeracityShellExtension\VeracityTortoise.dll

Note for 64-bit users: Windows Explorer on 64-bit systems is a 64-bit process. You must build Veracity as 64-bit in order to integrate with it.