1GPT-BUILD(8) User Contributed Perl Documentation GPT-BUILD(8)
2
3
4
6 gpt-build - Builds and installs GPT source packages and bundles.
7
9 gpt-build [options] [macros] [source packages] flavors ...
10
11 Options:
12 -verbose Print copious output
13 -help Print usage
14 -man Print man page.
15 -version Print GPT version.
16 -installdir=path_to_installation Override $GLOBUS_LOCATION
17 -builddir=path_to_build directory Directory to unpack tarfiles
18 -logdir=log_file_directory Directory for package logs
19 -srcdir=source_directory Directory containing a source package
20 -static Build static executables
21 -force Force rebuilds
22 -update Rebuild if newer
23 -disable-version-checking Ignore versions in package dependencies.
24 -std-flavors Build all std flavors.
25 -all-flavors Build all of the flavors
26 -coresrc Override installed globus_core pkg
27 -nosrc Only install the flavors
28 [macro=value] Macro definitions
29 [list of flavors to build] Flavors that define the build options
30 [list of source packages] Tarfiles of source bundles or packages
31
33 gpt-build Builds and installs software from source distributions. The
34 script reads the build instructions for each source distribution from a
35 package metadata file called pkg_data_src.gpt. If no instructions are
36 found the script uses the default instructions described in
37 Grid::GPT::PkgMngmt::Build.
38
39 Multiple packages can be built by passing in multiple -srcdir arguments
40 or multiple source packages and or bundles. For now these have to be
41 passed in in dependent order ie. if package foo needs package fee's
42 headers to build then fee should come first.
43
44 gpt-build does not create binary packages as globus-build does. This
45 is done by a seperate script called gpt-pkg.
46
48 Build flavors are character string labels that represent a set of
49 compiler and linker options defined during the building of the
50 globus_core package. Predefined flavors can be listed by using the gpt-
51 flavor-configuration script. Packages can be built with any installed
52 flavor. globus_core can only be built with pre-defined flavors.
53 globus_core needs to be built by hand (i.e. ./configure|make|make
54 install) to install a custom build flavor.
55
57 Installed files such as executables that are found in pgm and
58 ptm_static packages will overwrite one another when multiple flavors of
59 the same package are built. Thus only the files from the last flavor
60 built will be present after a gpt-build run. To preserve multiple
61 flavors of these files, they are automatically copied into flavored
62 subdirectories. For example, the program $GLOBUS_LOCATION/bin/foo will
63 be copied into the location $GLOBUS_LOCATION/bin/gcc32/shared if it was
64 built with dynamically with the gcc32 flavor. These files are
65 retrieved by gpt-pkg.
66
68 -srcdir Specifies the where the source directory is. This is used by
69 developers to build out of a repository..
70
71 -installdir
72 Specifies the where the install directory is. This directory
73 will be where the targets are installed before being archived.
74 Note that this directory needs contain the installation targets
75 of all of the packages which satisfy build dependencies in
76 addition to the installation targets of the package being
77 built. Because of this, installation targets are not removed
78 after the package is archived. Because different flavors of
79 program packages conflict with each other, the last flavor
80 built is the flavor of the installed files. For each flavor,
81 gpt-build makes a copy of each installed file in a program
82 package and puts the copy in a flavored subdirectory.
83
84 -builddir
85 Specifies the where the source tar files should be untarred and
86 the code is built.
87
88 -force Tells gpt-build to rebuild a package even if it is already
89 installed. The default behavior is to skip any packages that
90 have been built before.
91
92 -update Tells gpt-build to build even if an older version is installed.
93
94 -verbose
95 Prints out all of the build messages.
96
97 -std-flavors
98 Build the globus_core package with all of the flavor choices
99 marked as standard in the flavor configuration file. All of
100 the other packages will be built with all of the flavors
101 sucessfully installed by globus_core.
102
103 -all-flavors
104 Build the globus_core package with all of the flavor choices
105 marked as standard in the flavor configuration file. All of
106 the other packages will be built with all of the flavors
107 sucessfully installed by globus_core.
108
109 -nosrc Just install the listed flavors. Don't build any source code.
110
111 -coresrc
112 Use this version of globus_core source rather than the one
113 found in $GPT_LOCATION/share/globus/globus_core-src.tar.gz.
114
115 -disable-version-checking
116 GPT 1.x scripts neglected to check the version numbers of
117 packages during dependency checks. Because of this GPT bundles
118 were released that have errors in their dependency data. This
119 flag is provided so that these packages can still be used.
120 NOTE that once this flag is used, the version checking is
121 disabled permanently for the installation pointed to by
122 $GLOBUS_LOCATION. This condition can only be removed by
123 deleting the file
124 $GLOBUS_LOCATION/share/globus/disable_version_checking.
125
126 -flavor-cfg=FILE
127 Use the flavor configurations found in FILE. The default
128 configuration file is
129 $GPT_LOCATION/share/globus/globus_flavor_labels.conf
130
131 -logdir=DIRECTORY
132 Store package logs of build messages in DIRECTORY. This option
133 also sets -verbose. The default directory is ./logs.
134
135 -help Print a brief help message and exits.
136
137 -man Prints the manual page and exits.
138
139 -version
140 Prints the version of GPT and exits.
141
143 Build macros are perl routines and variables that are used by gpt-build
144 while building packages. These macros are embedded in the build
145 instructions part of the package's metadata file. Some of these macros
146 can be set from the command line using the following format:
147
148 <NAME>_GPTMACRO='new value'
149
150 Note that even though this feature seems extremely flexible, it has not
151 been thoroughly tested mainly because the authors have not been able to
152 figure out what people will want to do with these macros. Further
153 details are found in the Grid::GPT::PkgMngmt::BuildMacros manpage.
154
156 gpt-pkg(8) gpt-bundle(8) gpt-install(8) BuildMacros(3)
157
159 Michael Bletzinger <mbletzin.ncsa.uiuc.edu> and Eric Blau
160 <blau.mcs.anl.gov>
161
162
163
164perl v5.12.3 2011-03-24 GPT-BUILD(8)