The -buildpkg option can build the target source package or directory into binary form in the given flavor and install it to $GLOBUS_LOCATION. This is very similar to running gpt-build on the source package or source directory with the addition that the build tools will preform all necessary bootstrapping preparations on the source directory before compilation. In addition, the build tools can locate the source directory or source package from predetermined locations freeing the developer of this responsibility. The following usage applies:
uberBuild -buildpkg [ -compiler ] [ -srcdir ] [-pkgdir ] [ -fast ] [ -flavor ] [ -pkgconf [ variable substitutions ] ] [ package names ] [ src packages ]
The -compiler option species the compiler to use, for instance gcc32, gcc64 and vendorcc32 are common values.
The -flavor option specifies the flavor to build the package with. Common values for this option are pthr, dbg and dbgpthr. The value of this option is combined with the given compiler to determine the ultimate value. This option is not required as some package flavors only consist of the compiler used.
The -srcdir option specifies the source directory contain raw sources to build from. This option is not necessary with the -pkgconf option.
The -pkgconf option specifies a package configuration file previous generated from the source directory.
The -pkgdir option species where source packages should be placed.
The -fast option species that the build tools should make optimizations when possible. When building a package into binary form, an optimization is to:
Skip the build if the package is already installed to $GLOBUS_LOCATION
Use an available source package if one is available. This optimization avoids the bootstrap processing required when working on source directories
The last two items, "package names" and "src packages" refer to either the name of a package that exists in -srcdir or the name of a GPT source package such as globus_common-3.7.tar.gz