-{section: Building Condor prior to 7.5.5 on Windows}
+{section: Building HTCondor prior to 7.5.5 on Windows}
<html><h2> Requirements </h2></html>
@@ -31,7 +31,7 @@
<html><h3> Microsoft Windows Server 2003 SP1 Platform SDK </h3></html>
-If you are building Condor on an x64 machine then after installing the Platform SDKs, you will either need to move or copy them to
+If you are building HTCondor on an x64 machine then after installing the Platform SDKs, you will either need to move or copy them to
C:\Program Files
@@ -39,7 +39,7 @@
<html><h3> Visual Studio 2008: Build and Run </h3></html>
-Parallel builds should be disabled (*these can actually be used now, Ben Burnett [2009-07-10]*). As much as we would love to support building projects in parallel, the constraints of current code-base will not allow for it. By default, Visual Studio is configured to build _x_ number of projects in parallel, where _x_ is the number of physical CPUs or cores you have on the machine; you will need to disable this feature before being able to successfully build Condor. These changes can be made as follows:
+Parallel builds should be disabled (*these can actually be used now, Ben Burnett [2009-07-10]*). As much as we would love to support building projects in parallel, the constraints of current code-base will not allow for it. By default, Visual Studio is configured to build _x_ number of projects in parallel, where _x_ is the number of physical CPUs or cores you have on the machine; you will need to disable this feature before being able to successfully build HTCondor. These changes can be made as follows:
1: From the *Tools* menu, select *Options...*
1: In the *Options* dialog, expand *Project and Solutions*, and select *Build and Run*
@@ -59,7 +59,7 @@
In NMI, the test lab we use here, you will also need to create a user account from which we will derive the slot user profiles from. This is a fairly simple process, but for compleatness, the steps are included.
-For details on creating the template account Condor, please refer to WindowsUserProfiles.
+For details on creating the template account HTCondor, please refer to WindowsUserProfiles.
<html><h4> NMI Cygwin install </h3></html>
@@ -86,11 +86,11 @@
<html><h3> <code>gsoap.mak</code> Eccentricities </h3></html>
-A temporary directory has been hard-coded into =gsoap.mak= (i.e. *C:\Temp*). The presence of this directory is required for Condor to compile. This will be changed for future releases.
+A temporary directory has been hard-coded into =gsoap.mak= (i.e. *C:\Temp*). The presence of this directory is required for HTCondor to compile. This will be changed for future releases.
<html><h2> Building </h2></html>
-You can build Condor one of two ways: from the command-line, or from the IDE. Both require that you be in =C:\workspace\source\msbuild= directory. See GitingTheCode for further details on getting the source.
+You can build HTCondor one of two ways: from the command-line, or from the IDE. Both require that you be in =C:\workspace\source\msbuild= directory. See GitingTheCode for further details on getting the source.
<html><h3> From the Command-line </h3></html>
@@ -124,7 +124,7 @@
<html><h2> Trouble Shooting </h2></html>
-In some rare cases the local computer's environment may interfere with building Condor: most of the time this is due to an incompatibility in SDK versions. By default, newer versions of *Visual Studio* install the, at the time, up-to-date SDKs. This is usually found in the *%ProgramFiles%\Microsoft SDKs* folder. If there is a problem when running the build scripts, this is likely the culprit. It also contains the same configuring scripts that the *Platform SDKs* do; however, they do not support Windows 2000. A sure sign that this is incorrectly configured is easy to diagnose: the scripts have the name, but take different command-line options, so you will see an error after running =set_env.bat=. You can remedy this by renaming *%ProgramFiles%\Microsoft SDKs* to something else while developing or compiling the Condor software. This will not be a problem when Condor drops support for *Windows 2000*.
+In some rare cases the local computer's environment may interfere with building HTCondor: most of the time this is due to an incompatibility in SDK versions. By default, newer versions of *Visual Studio* install the, at the time, up-to-date SDKs. This is usually found in the *%ProgramFiles%\Microsoft SDKs* folder. If there is a problem when running the build scripts, this is likely the culprit. It also contains the same configuring scripts that the *Platform SDKs* do; however, they do not support Windows 2000. A sure sign that this is incorrectly configured is easy to diagnose: the scripts have the name, but take different command-line options, so you will see an error after running =set_env.bat=. You can remedy this by renaming *%ProgramFiles%\Microsoft SDKs* to something else while developing or compiling the HTCondor software. This will not be a problem when HTCondor drops support for *Windows 2000*.
Put shortly, if you do not see the following two lines in the build output:
@@ -137,7 +137,7 @@
<html><h2> Packaging </h2></html>
-If you wish to package up Condor the way we do on our web page (as a self-contained MSI installer file and a ZIP file), then follow these instructions.
+If you wish to package up HTCondor the way we do on our web page (as a self-contained MSI installer file and a ZIP file), then follow these instructions.
<html><h3> Packaging a build from source code </h3></html>
Starting from the source directory, here is an example of the commands you would enter:
@@ -154,7 +154,7 @@
1: move c:\temp\public c:\temp\condor-v7.5.2
1: rmdir c:\temp\condor-v7.5.2\testbin
1: rmdir c:\temp\condor-v7.5.2\logs
-1: git checkout V7_5_2 _(note: you need to checkout from git the same version of Condor that NMI built, as the packaging scripts and directives themselves are only found in the source code and not in the results.tar file)_
+1: git checkout V7_5_2 _(note: you need to checkout from git the same version of HTCondor that NMI built, as the packaging scripts and directives themselves are only found in the source code and not in the results.tar file)_
1: cd CONDOR_SRC\msconfig
1: dopackaging.bat c:\temp\condor-7.5.2 c:\temp
1: After about 15 minutes, =condor-7.5.2-winnt50-x86.msi= and =condor-7.5.2-winnt50-x86.zip= will waiting for you in =c:\temp=
