2: Install Visual Studio. Add it to your PATH.
*::Visual Studio Express (Free to anyone) https://www.microsoft.com/express/Downloads/
-*::Visual Studio 2008. Paid.
+*::Visual Studio 2012. Paid.
*::: UW Madison staff can use MSDNAA: http://msdn04.e-academy.com/wiscmad_cs ; contact the CSL lab for an account if you don't have one. You'll get a .img file of the DVD. You can use 7-zip to extract the contents and install from there instead of burning a DVD or installing DVD emulation software.
3: [Optional] Start Visual Studio and Open Tools->Options under "Projects and Solutions" click on VC++ Directories and add the following to the *Executable* directories. This is not needed if you use =msconfig\set_build_env.bat= to set the PATH before you build.
@@ -26,12 +26,6 @@
3: Install Active Perl. Add it to your PATH.
*::http://www.activestate.com/activeperl/downloads
-4: Install the .NET 2.0 redistributable (Should only be necessary on Windows XP and earlier)
-*::https://www.microsoft.com/downloads/en/details.aspx?FamilyID=0856eacb-4362-4b0d-8edd-aab15c5e04f5&displaylang=en
-
-5: [Optional] Install the Windows Platform SDK. (may depend on .NET 2.0). Any version of the Platform SDK should be fine. SDK 6.1 and 7.0 are both known to work. This is not required if you have Visual Studio 2008 professional.
-*::http://msdn.microsoft.com/en-us/windows/bb980924
-
1: [Optional but Recommended] Install 7-zip. Add it to your PATH. 7-zip is not needed to build, but it is needed to make the HTCondor .ZIP file. You will not be able to build the PACKAGE target witout 7-zip.
*::http://www.7-zip.org/download.html
@@ -43,11 +37,11 @@
{subsection: Building }
-1.) Open a windows commmand prompt
+1.) Open a windows commmand prompt (you can use the command prompt provided by the Visual Studio installation "%appdata%\Microsoft\Windows\Start Menu\Programs\Microsoft Visual Studio 2012\Visual Studio Tools\Developer Command Prompt for VS2012")
2.) Checkout origin/master from the git repository, or download the HTCondor Sources http://www.cs.wisc.edu/condor/downloads-v2/download.pl
-3.) navigate to CONDOR_SRC
+3.) navigate to CONDOR_SRC the root directory
4.) add cmake\bin to your PATH if it is not already. One way to do this is to execute =CONDOR_SRC\msconfig\set_build_env.bat=. This will setup PATH, LIB, and INCLUDE environment variables to build HTCondor. If this batch file cannot find cmake.exe It will report an error.
@@ -58,7 +52,7 @@
6.) The the cmake build supports both in-source and out-of-source builds. For in-source builds execute
{code}
-cmake -G "Visual Studio 9 2008" .
+cmake -G "Visual Studio 11 2012" .
{endcode}
for out-of-source builds, navigate to the build destination folder and execute cmake; passing it the path to the HTCondor sources. For example
{code}
@@ -66,7 +60,7 @@
set _condor_sources=%CD%
md c:\scratch\condor\build_dest
cd /d c:\scratch\condor\build_dest
-cmake CMakeLists.txt -G "Visual Studio 9 2008" %_condor_sources%
+cmake CMakeLists.txt -G "Visual Studio 11 2012" %_condor_sources%
{endcode}
This will create Visual Studio Project and Solution files to build HTCondor.
Many options can be passed to cmake, see CondorCmakeBuildOptions for more information. You can also use the cmake-gui to set options.
@@ -104,34 +98,3 @@
cd c:\scratch\condor\release_dir
etc\WiX\do_wix.bat %CD% c:\scratch\condor\Condor-X.Y.Z-winnt-x86.msi
{endcode}
-
-
-{section: Gotchas}
-{subsection: SDK corruption of VC setup}
-Installation of the new Microsoft SDK (6.1 aka Server 2008) can leave an existing VC 9.0 installation with a corrupted setup bat file. After installing the SDK, check the contents of =C:\Program Files\Microsoft Visual Studio 9.0\VC\bin\vcvars32.bat= {linebreak}If you see the lines:
-
-{code}
-@SET FrameworkDir=Framework32
-@SET FrameworkVersion=v2.0.50727
-{endcode}
-change them to:
-{code}
-@SET FrameworkDir=C:\Windows\Microsoft.NET\Framework
-@SET FrameworkVersion=v2.0.50727
-@SET Framework35Version=v3.5
-{endcode}
-
-Also, a portion of the PATH variable may have an incorrect entry which can lead to problems in the CMD interpreter. If in the same file you see a PATH entry like:
-{code}
-%FrameworkDir%\%Framework35Version%\Microsoft .NET Framework 3.5 (Pre-Release Version);
-{endcode}
-change it to point to the correct version like:
-{code}
-%FrameworkDir%\%Framework35Version%\Microsoft .NET Framework 3.5 SP1;
-{endcode}
-
-{subsection: Environment variable expansion}
-The new =SetEnv.cmd= shipped in the 6.1 SDK requires that both command extensions and environment variable expansion be turned on. Either use the "CMD Shell" shortcut installed with the Windows SDK or ensure that CMD is launch with the /V:ON and /E:ON parameters. For example:
-{code}
-CMD /V:ON /E:ON
-{endcode}
