{section: Overview}
-As of version 7.5.5, Condor uses cmake to configure the build. For instructions on building Condor prior to that, see BuildingCondorOnUnixOld.
+As of version 7.5.5, HTCondor uses cmake to configure the build. For instructions on building HTCondor prior to that, see BuildingCondorOnUnixOld.
{section: Confirm the build environment}
The README.building does a decent job of covering this, but usually
@@ -9,14 +9,14 @@
{subsection: Space Needed for a Full Build}
-You may need around 6 Gigs to build a releasable package of Condor. If you
+You may need around 6 Gigs to build a releasable package of HTCondor. If you
just want to build eveything up to the releasable package, then you might
need only 3 Gigs or so.
{subsection: Required Prereqs}
One needs, as a good start these revisions, or later, of these tools:
wget-1.9.1, tar 1.14, autoconf-2.59. If you are on a recent linux-flavor
-machine, building Condor is pretty easy, the farther you get into
+machine, building HTCondor is pretty easy, the farther you get into
the fringe architectures, like ia64 hpux 11, the more prereqs you may
need. Luckily, the configure output is pretty good about telling you
about any tools you need to update.
@@ -41,10 +41,10 @@
{endcode}
{subsection: From our download pages}
-If you are building Condor sources from our
+If you are building HTCondor sources from our
{link: http://www.cs.wisc.edu/condor/downloads-v2/download.pl download}
page. Then download the source tarball, it'll have a name similar to
-=condor_src-X.Y.Z-all-all.tar.gz=. X.Y.Z represents the version of Condor
+=condor_src-X.Y.Z-all-all.tar.gz=. X.Y.Z represents the version of HTCondor
for which the source creates.
When you untar the source tarball, what you get is remarkably similar to
@@ -53,11 +53,11 @@
pages needed by our packaging scripts.
{subsection: Externals required for Building}
-Condor may use a sizable collection of externals which implement various feature
-sets for Condor. Some examples are Kerberos, PostgreSQL, Globus. Condor sources
+HTCondor may use a sizable collection of externals which implement various feature
+sets for HTCondor. Some examples are Kerberos, PostgreSQL, Globus. HTCondor sources
include an =externals/= directory which contains URLs to locate the required
externals and patches to be applied. There is only a small number of externals
-that Condor absolutely requires to build, these are usually quite portable.
+that HTCondor absolutely requires to build, these are usually quite portable.
{subsection: Required Prereqs}
@@ -65,11 +65,11 @@
cmake 2.8.3, wget-1.9.1, tar 1.14, autoconf-2.59. For a more complete list, run =nmi_tools/glue/SubmitInfo.pm= and look at the listed prereqs for a platform as similar to the one you are using as possible.
{subsection: Externals required for Building}
-Condor may use a sizable collection of externals which implement various feature
-sets for Condor. Some examples are =Kerberos=, =OpenSSL=, =Globus=. There are only a small number of externals
-that Condor absolutely requires to build; these are usually quite portable.
+HTCondor may use a sizable collection of externals which implement various feature
+sets for HTCondor. Some examples are =Kerberos=, =OpenSSL=, =Globus=. There are only a small number of externals
+that HTCondor absolutely requires to build; these are usually quite portable.
There are
-two ways to link with external packages, using the blessed and patched versions of the packages from the UW Condor externals collection, or using the native libraries installed on the build machine. We'll call these the 'UW' way and the 'proper' way. To get externals the UW way, Condor sources
+two ways to link with external packages, using the blessed and patched versions of the packages from the UW HTCondor externals collection, or using the native libraries installed on the build machine. We'll call these the 'UW' way and the 'proper' way. To get externals the UW way, HTCondor sources
include an =externals/= directory which contains URLs to locate the required
externals and patches to be applied. To get externals the 'proper' way, you'll need to use your system's package manager to install the necessary development libraries.
@@ -77,14 +77,14 @@
See the new build {link: https://condor-wiki.cs.wisc.edu/index.cgi/wiki?p=BuildModernization instructions}
-The common options for configuring Condor to be built the 'UW way' are passed to cmake by running =configure_uw=. This will configure the build to use the UW externals collection rather than local system libraries.
+The common options for configuring HTCondor to be built the 'UW way' are passed to cmake by running =configure_uw=. This will configure the build to use the UW externals collection rather than local system libraries.
Additional arguments to cmake may be passed on the command line of =configure_uw=. On most common platforms, no additional build options are required. For other platforms, there are several ways to explore the build options:
*: ccmake
*: cmake-gui
*: cmake -i
-*: Use =nmi_tools/glue/SubmitInfo.pm=, which shows the build options that are used to build Condor on a wide variety of platforms in the NMI build system.
+*: Use =nmi_tools/glue/SubmitInfo.pm=, which shows the build options that are used to build HTCondor on a wide variety of platforms in the NMI build system.
*:: To list the platforms that SubmitInfo.pm knows:
*::: =./nmi_tools/glue/SubmitInfo.pm -l=
*:: To list the options for a particular platform
