1 nightly(1) User Commands nightly(1)
2
3
4
5 NAME
6 nightly - build an OS-Net consolidation overnight
7
8 SYNOPSIS
9 nightly [-in] [-V VERS] <env_file>
10
11 DESCRIPTION
12 nightly, the mother of all build scripts, can bringover, build,
13 archive, package, error check, and generally do everything it takes to
14 turn OS/Net consolidation source code into useful stuff. It is
15 customizable to permit you to run anything from a simple build to all
16 of the cross-checking a gatekeeper needs. The advantage to using
17 nightly is that you build things correctly, consistently and
18 automatically, with the best practices; building with nightly can mean
19 never having to say you're sorry to your gatekeeper.
20
21 More specifically, nightly performs the following tasks, in order, if
119
120 -A Check for ABI discrepancies in .so files. It is only
121 required for shared object developers when there is an
122 addition, deletion or change of interface in the .so files.
123
124 -C Check for cstyle/hdrchk errors
125
126 -f Check for unreferenced files. Since the full workspace must
127 be built in order to accurately identify unreferenced files,
128 -f is ignored for incremental (-i) builds, or builds that do
129 not include -l, and -p.
130
131 -r Check the ELF runtime attributes of all dynamic objects
132
133 -l Do "make lint" in $LINTDIRS (default: $SRC n)
134
135 -N Do not run protocmp or checkpaths (note: this option is not
136 recommended, especially in conjunction with the -p option)
137
138 -w Report which proto area objects differ between this and the
139 last build. See wsdiff(1) for details. Note that the proto
140 areas used for comparison are the last ones constructed as
141 part of the build. As an example, if both a non-debug and
142 debug build are performed (in that order), then the debug
143 proto area will be used for comparison (which might not be
144 what you want).
145
146 Groups of options
147
148 -G Gate keeper default group of options (-u)
149
150 -I Integration engineer default group of options (-mpu)
151
152 -R Default group of options for building a release (-mp)
153
154
155 Miscellaneous options
156
157 -V VERS set the build version string to VERS, overriding VERSION
158
159
160 ENVIRONMENT VARIABLES
161 Here is a list of prominent environment variables that nightly
368 SYS_POST_NIGHTLY
369 This is reserved for per-build-machine customizations, and runs
370 immedately after POST_NIGHTLY.
371
372 FILES
373 /etc/nightly.conf
374
375 If present, nightly executes this file just prior to executing the env
376 file.
377
378 EXAMPLES
379 Start with the example file in usr/src/tools/env/developer.sh (or
380 gatekeeper.sh), copy to myenv and make your changes.
381
382 # grep NIGHTLY_OPTIONS myenv
383 NIGHTLY_OPTIONS="-ACrlapDm"
384 export NIGHTLY_OPTIONS
385 # /opt/onbld/bin/nightly -i myenv
386
387 SEE ALSO
388 bldenv(1)
389
390
391
392 January 28, 2014 nightly(1)
|
1 nightly(1ONBLD) illumos Build Tools nightly(1ONBLD)
2
3
4
5 NAME
6 nightly - build an OS-Net consolidation overnight
7
8 SYNOPSIS
9 nightly [-in] [-V VERS] <env_file>
10
11 DESCRIPTION
12 nightly, the mother of all build scripts, can bringover, build,
13 archive, package, error check, and generally do everything it takes to
14 turn OS/Net consolidation source code into useful stuff. It is
15 customizable to permit you to run anything from a simple build to all
16 of the cross-checking a gatekeeper needs. The advantage to using
17 nightly is that you build things correctly, consistently and
18 automatically, with the best practices; building with nightly can mean
19 never having to say you're sorry to your gatekeeper.
20
21 More specifically, nightly performs the following tasks, in order, if
119
120 -A Check for ABI discrepancies in .so files. It is only
121 required for shared object developers when there is an
122 addition, deletion or change of interface in the .so files.
123
124 -C Check for cstyle/hdrchk errors
125
126 -f Check for unreferenced files. Since the full workspace must
127 be built in order to accurately identify unreferenced files,
128 -f is ignored for incremental (-i) builds, or builds that do
129 not include -l, and -p.
130
131 -r Check the ELF runtime attributes of all dynamic objects
132
133 -l Do "make lint" in $LINTDIRS (default: $SRC n)
134
135 -N Do not run protocmp or checkpaths (note: this option is not
136 recommended, especially in conjunction with the -p option)
137
138 -w Report which proto area objects differ between this and the
139 last build. See wsdiff(1ONBLD) for details. Note that the
140 proto areas used for comparison are the last ones constructed
141 as part of the build. As an example, if both a non-debug and
142 debug build are performed (in that order), then the debug
143 proto area will be used for comparison (which might not be
144 what you want).
145
146 Groups of options
147
148 -G Gate keeper default group of options (-u)
149
150 -I Integration engineer default group of options (-mpu)
151
152 -R Default group of options for building a release (-mp)
153
154
155 Miscellaneous options
156
157 -V VERS set the build version string to VERS, overriding VERSION
158
159
160 ENVIRONMENT VARIABLES
161 Here is a list of prominent environment variables that nightly
368 SYS_POST_NIGHTLY
369 This is reserved for per-build-machine customizations, and runs
370 immedately after POST_NIGHTLY.
371
372 FILES
373 /etc/nightly.conf
374
375 If present, nightly executes this file just prior to executing the env
376 file.
377
378 EXAMPLES
379 Start with the example file in usr/src/tools/env/developer.sh (or
380 gatekeeper.sh), copy to myenv and make your changes.
381
382 # grep NIGHTLY_OPTIONS myenv
383 NIGHTLY_OPTIONS="-ACrlapDm"
384 export NIGHTLY_OPTIONS
385 # /opt/onbld/bin/nightly -i myenv
386
387 SEE ALSO
388 bldenv(1ONBLD)
389
390
391
392 January 28, 2014 nightly(1ONBLD)
|