Building Condor on Vista

From Ben's Writing

Jump to: navigation, search

Contents

[edit]

Requirements

  • Vista Ultimate;
  • Visual Studio 2005 Team Suite;
    • Visual Studio 2005 Service Pack 1 (VS80sp1-KB926601-X86-ENU.exe)
    • Visual Studio 2005 Service Pack 1 Update for Windows Vista (VS80sp1-KB932232-X86-ENU.exe)
  • MSDN (optional)
  • Platform SDKs for Windows Server 2003: It turns out that if Condor is built on Vista with the Vista Platform SDKs, then it is not possible to run the resulting binary on Windows 2000. This is because the Vista Platform SDKs can only target as far back as XP and Windows Server 2003;
  • Cygwin.
  • ActiveState Perl;
[edit]

Installation

  • Install all the packages to their default locations, as some of our scripts are reliant on these locations. This is no longer necessarily true, as we look to the system drive for the binaries, rather than the original hard-coded C:\ drive.
  • The order in which you install them is also important; for instance, the Visual Studio service pack should be installed after Visual Studio is installed. Also, for proper integration, the Windows SDK should be installed after Visual Studio has completed its installation.
[edit]

Configuration

Some of this is directly from the NMI installation instructions

[edit]

Cygwin

  • Right-click your Cygwin shortcut, select Properties > Advanced ... > Check Run as administrator
  • Click OK
[edit]

Command Prompt

  • Right-click your Command Prompt shortcut, in the Target text box enter: 
%comspec% /v:on ...

where ... were the original optional parameters. The /v:on "[e]nables delayed environment variable expansion" which are used in the new MS Platform SDK environment scripts (they us "!" instead of "%" to surround variables). If we don't use this option, these new script will corrupt the environment variables.

  • Click OK

Alternatively, one can make the settings permanent across all command prompts using the following registry hive: 

Windows Registry Editor Version 5.00 

[HKEY_CURRENT_USER\Software\Microsoft\Command Processor]
"DelayedExpansion"=dword:00000001
  • Also, while you are in the Command Prompt properties dialog: click Advanced ... > Check Run as administrator

  • Right-click your Command Prompt shortcut, select Properties > Advanced ... > Check Run as administrator
  • Click OK
[edit]

Microsoft Visual Studio 2005

  • Right-click your Microsoft Visual Studio 2005 shortcut, select Properties > Advanced ... > Check Run as administrator
  • Click OK
[edit]

File System

  • Make sure to create a C:\Temp directory. Although a user's environment contains variables that point to their personal temporary store, these will not work with perl. So, if you see weird errors about patches failing to find files that are clearly there, then double check that the temporary directory has not accidentaly been blown away. (NOTE: Do not create this using Cygwin; it has a bad habit of adding all sorts of funky permissions that you'll end up having to change.)
[edit]

Notes

  • set_vars.bat has an extra variable USING_VC8_TO_BUILD which makes the externals' build process behave differently (but it is already set, so there is nothing to do other than be aware of its existence— and that we should get rid of all of it (including the if's in the externals' *.bat files) once we have dropped support for VC6)
  • Also see Editing and Building the Condor Documentation
Retrieved from "http://ben.versionzero.org/wiki/Building_Condor_on_Vista"
Personal tools