Print this page
4030 remove useless nightly/bldenv options
Reviewed by: Andy Stormont <andyjstormont@gmail.com>
| Split |
Close |
| Expand all |
| Collapse all |
--- old/usr/src/tools/scripts/nightly.1
+++ new/usr/src/tools/scripts/nightly.1
1 1 .\" "
2 2 .\" " The contents of this file are subject to the terms of the
3 3 .\" " Common Development and Distribution License (the "License").
4 4 .\" " You may not use this file except in compliance with the License.
5 5 .\" "
6 6 .\" " You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
7 7 .\" " or http://www.opensolaris.org/os/licensing.
8 8 .\" " See the License for the specific language governing permissions
9 9 .\" " and limitations under the License.
10 10 .\" "
11 11 .\" " When distributing Covered Code, include this CDDL HEADER in each
12 12 .\" " file and include the License file at usr/src/OPENSOLARIS.LICENSE.
13 13 .\" " If applicable, add the following below this CDDL HEADER, with the
14 14 .\" " fields enclosed by brackets "[]" replaced with your own identifying
15 15 .\" " information: Portions Copyright [yyyy] [name of copyright owner]
16 16 .\" "
17 17 .\" " CDDL HEADER END
18 18 .\" "
19 19 .\" "Copyright (c) 1999, 2010, Oracle and/or its affiliates. All rights reserved.
20 20 .\" "Copyright 2012 Joshua M. Clulow <josh@sysmgr.org>
21 21 .\" "
22 22 .TH nightly 1 "6 July 2010"
23 23 .SH NAME
24 24 .I nightly
25 25 \- build an OS-Net consolidation overnight
26 26 .SH SYNOPSIS
27 27 \fBnightly [-in] [-V VERS] <env_file>\fP
28 28 .LP
29 29 .SH DESCRIPTION
30 30 .IX "OS-Net build tools" "nightly" "" "\fBnightly\fP"
31 31 .LP
32 32 .I nightly,
33 33 the mother of all build scripts,
34 34 can bringover, build, archive, package, error check, and
35 35 generally do everything it takes to
36 36 turn OS/Net consolidation source code into useful stuff.
37 37 It is customizable to permit you to run anything from a
38 38 simple build to all of the cross-checking a gatekeeper
39 39 needs. The advantage to using
40 40 .I nightly
41 41 is that you build things correctly, consistently and
42 42 automatically, with the best practices; building with
43 43 .I nightly
44 44 can mean never having to say you're sorry to your
45 45 gatekeeper.
46 46 .LP
47 47 More
48 48 specifically,
49 49 .I nightly
50 50 performs the following tasks, in order, if
51 51 all these things are desired:
52 52 .LP
53 53 .RS
54 54 .TP
55 55 \(bu
56 56 perform a "make clobber" to clean up old binaries
57 57 .TP
58 58 \(bu
59 59 bringover from the identified parent gate/clone
60 60 .TP
61 61 \(bu
62 62 perform non-DEBUG and DEBUG builds
63 63 .TP
64 64 \(bu
65 65 list proto area files and compare with previous list
66 66 .TP
67 67 \(bu
68 68 copy updated proto area to parent
69 69 .TP
70 70 \(bu
71 71 list shared lib interface and compare with previous list
72 72 .TP
73 73 \(bu
74 74 perform a "make lint" of the kernel and report errors
75 75 .TP
76 76 \(bu
77 77 perform a "make check" to report hdrchk/cstyle errors
78 78 .TP
79 79 \(bu
80 80 report the presence of any core files
81 81 .TP
82 82 \(bu
83 83 check the ELF runtime attributes of all dynamic objects
84 84 .TP
85 85 \(bu
86 86 check for unreferenced files
87 87 .TP
88 88 \(bu
89 89 report on which proto area objects have changed (since the last build)
90 90 .TP
91 91 \(bu
92 92 report the total build time
93 93 .TP
94 94 \(bu
95 95 save a detailed log file for reference
96 96 .TP
97 97 \(bu
98 98 mail the user a summary of the completed build
99 99 .RE
100 100 .LP
101 101 The actions of the script are almost completely determined by
102 102 the environment variables in the
103 103 .I env
104 104 file, the only necessary argument. Ths only thing you really
105 105 need to use
106 106 .I nightly
107 107 is an
108 108 .I env
109 109 file that does what you want.
110 110 .LP
111 111 Like most of the other build tools in usr/src/tools, this script tends
112 112 to change on a fairly regular basis; do not expect to be able to build
113 113 OS/Net with a version of nightly significantly older than your source
114 114 tree. It has what is effectively a Consolidation Private relationship
115 115 to other build tools and with many parts of the OS/Net makefiles,
116 116 although it may also be used to build other consolidations.
117 117 .LP
118 118 .SH NIGHTLY_OPTIONS
119 119 The environment variable NIGHTLY_OPTIONS controls the actions
120 120 .I nightly
121 121 will take as it proceeds.
122 122 The -i, -n, +t and -V options may also be used from the command
123 123 line to control the actions without editing your environment file.
124 124 The -i and -n options complete the build more quickly by bypassing
125 125 some actions. If NIGHTLY_OPTIONS is not set, then "-Bmt" build
126 126 options will be used.
127 127
128 128 .B Basic action options
129 129 .TP 10
130 130 .B \-D
131 131 Do a build with DEBUG on (non-DEBUG is built by default)
132 132 .TP
133 133 .B \-F
134 134 Do _not_ do a non-DEBUG build (use with -D to get just a DEBUG build)
135 135 .TP
136 136 .B \-M
137 137 Do not run pmodes (safe file permission checker)
138 138 .TP
139 139 .B \-i
140 140 Do an incremental build, suppressing the "make clobber" that by
141 141 default removes all existing binaries and derived files. From the
142 142 command line, -i also suppresses the lint pass and the cstyle/hdrchk
143 143 pass
144 144 .TP
145 145 .B \-n
146 146 Suppress the bringover so that the build will start immediately with
147 147 current source code
148 148 .TP
149 149 .B \-o
150 150 Do an "old style" (pre-S10) build using root privileges to set OWNER
151 151 and GROUP from the Makefiles.
152 152 .TP
153 153 .B \-p
154 154 Create packages for regular install
155 155 .TP
156 156 .B \-U
157 157 Update proto area in the parent workspace
158 158 .TP
159 159 .B \-u
160 160 Update the parent workspace with files generated by the build, as follows.
161 161 .RS
162 162 .TP
163 163 \(bu
164 164 Copy proto_list_${MACH} and friends to usr/src in the parent.
165 165 .TP
166 166 \(bu
167 167 When used with -f, build a usr/src/unrefmaster.out in
168 168 the parent by merging all the usr/src/unref-${MACH}.out files in the
169 169 parent.
170 170 .TP
171 171 \(bu
172 172 When used with -A or -r, copy the contents of the resulting
173 173 ELF-data.${MACH} directory to usr/src/ELF-data.${MACH} in the parent
174 174 workspace.
175 175 .RE
176 176 .TP
177 177 .B \-m
178 178 Send mail to $MAILTO at end of build
179 179 .TP
180 180 .B \-t
181 181 Build and use the tools in $SRC/tools (default setting).
182 182 .TP
183 183 .B \+t
184 184 Use the build tools in "$ONBLD_TOOLS/bin".
185 185
186 186 .LP
187 187 .B Code checking options
188 188 .TP 10
189 189 .B \-A
190 190 Check for ABI discrepancies in .so files.
191 191 It is only required for shared object developers when there is an
192 192 addition, deletion or change of interface in the .so files.
193 193 .TP
194 194 .B \-C
195 195 Check for cstyle/hdrchk errors
196 196 .TP
197 197 .B \-f
198 198 Check for unreferenced files. Since the full workspace must be built
199 199 in order to accurately identify unreferenced files, -f is ignored for
200 200 incremental (-i) builds, or builds that do not include -l, and -p.
201 201 .TP
202 202 .B \-r
203 203 Check the ELF runtime attributes of all dynamic objects
204 204 .TP
205 205 .B \-l
206 206 Do "make lint" in $LINTDIRS (default: $SRC n)
207 207 .TP
208 208 .B \-N
209 209 Do not run protocmp or checkpaths (note: this option is not
210 210 recommended, especially in conjunction with the \-p option)
211 211 .TP
212 212 .B \-W
213 213 Do not report warnings (for freeware gate ONLY)
214 214 .TP
215 215 .B \-w
216 216 Report which proto area objects differ between this and the last build.
217 217 See wsdiff(1) for details. Note that the proto areas used for comparison
218 218 are the last ones constructed as part of the build. As an example, if both
219 219 a non-debug and debug build are performed (in that order), then the debug
220 220 proto area will be used for comparison (which might not be what you want).
221 221 .LP
222 222 .B Groups of options
223 223 .TP 10
|
↓ open down ↓ |
223 lines elided |
↑ open up ↑ |
224 224 .B \-G
225 225 Gate keeper default group of options (-u)
226 226 .TP
227 227 .B \-I
228 228 Integration engineer default group of options (-mpu)
229 229 .TP
230 230 .B \-R
231 231 Default group of options for building a release (-mp)
232 232
233 233 .LP
234 -.B Source Build options
235 -.TP 10
236 -.B \-S E | D | H
237 -Build the Export, Domestic, or Hybrid source product. Only Export and
238 -Domestic are truly buildable at this time.
239 -.TP 10
240 -.B \-S O
241 -Simulate an OpenSolaris build on a full tree. This can be used by
242 -internal developers to ensure that they haven't broken the build for
243 -external developers.
244 -.LP
245 -Source build options only make sense for a full internal tree (open
246 -and closed source). Only one source build option can be specified at
247 -a time.
248 -
249 -.LP
250 234 .B Miscellaneous options
251 235 .TP 10
252 -.B \-O
253 -generate deliverables for OpenSolaris. Tarballs containing signed
254 -cryptographic binaries and binaries
255 -of closed-source components are put in $CODEMGR_WS. (The
256 -cryptographic tarballs are copies of the
257 -ones that are put in the parent directory of
258 -$PKGARCHIVE.)
259 -.TP 10
260 236 .B \-V VERS
261 237 set the build version string to VERS, overriding VERSION
262 238 .TP
263 239 .B \-X
264 240 Copies the proto area and packages from the IHV and IHV-bin gates into the
265 241 nightly proto and package areas. This is only available on i386. See
266 242 .B REALMODE ENVIRONMENT VARIABLES
267 243 and
268 244 .B BUILDING THE IHV WORKSPACE
269 245 below.
270 246
271 247 .LP
272 248 .SH ENVIRONMENT VARIABLES
273 249 .LP
274 250 Here is a list of prominent environment variables that
275 251 .I nightly
276 252 references and the meaning of each variable.
277 253 .LP
278 254 .RE
279 255 .B CODEMGR_WS
280 256 .RS 5
281 257 The root of your workspace, including whatever metadata is kept by
282 258 the source code management system. This is the workspace in which the
283 259 build will be done.
284 260 .RE
285 261 .LP
286 262 .B PARENT_WS
287 263 .RS 5
288 264 The root of the workspace that is the parent of the
289 265 one being built. This is particularly relevant for configurations
290 266 with a main
291 267 workspace and build workspaces underneath it; see the
292 268 \-u and \-U
293 269 options as well as the PKGARCHIVE environment variable, for more
294 270 information.
295 271 .RE
296 272 .LP
297 273 .B BRINGOVER_WS
298 274 .RS 5
299 275 This is the workspace from which
300 276 .I nightly
301 277 will fetch sources to either populate or update your workspace;
302 278 it defaults to $CLONE_WS.
303 279 .RE
304 280 .LP
305 281 .B CLOSED_BRINGOVER_WS
306 282 .RS 5
307 283 A full Mercurial workspace has two repositories: one for open source
308 284 and one for closed source. If this variable is non-null,
309 285 .I nightly
310 286 will pull from the repository that it names to get the closed source.
311 287 It defaults to $CLOSED_CLONE_WS.
312 288 .LP
313 289 If $CODEMGR_WS already exists and contains only the open repository,
314 290 .I nightly
315 291 will ignore this variable; you'll need to pull the closed repository
316 292 by hand if you want it.
317 293 .RE
318 294 .LP
319 295 .B CLONE_WS
320 296 .RS 5
321 297 This is the workspace from which
322 298 .I nightly
323 299 will fetch sources by default. This is
324 300 often distinct from the parent, particularly if the parent is a gate.
325 301 .RE
326 302 .LP
327 303 .B CLOSED_CLONE_WS
328 304 .RS 5
329 305 This is the default closed-source Mercurial repository that
330 306 .I nightly
331 307 might pull from (see
332 308 .B CLOSED_BRINGOVER_WS
333 309 for details).
334 310 .RE
335 311 .LP
336 312 .B SRC
337 313 .RS 5
338 314 Root of OS-Net source code, referenced by the Makefiles. It is
339 315 the starting point of build activity. It should be expressed
340 316 in terms of $CODEMGR_WS.
341 317 .RE
342 318 .LP
|
↓ open down ↓ |
73 lines elided |
↑ open up ↑ |
343 319 .B ROOT
344 320 .RS 5
345 321 Root of the proto area for the build. The makefiles direct
346 322 installation of build products to this area and
347 323 direct references to these files by builds of commands and other
348 324 targets. It should be expressed in terms of $CODEMGR_WS.
349 325 .LP
350 326 If $MULTI_PROTO is "no", $ROOT may contain a DEBUG or non-DEBUG
351 327 build. If $MULTI_PROTO is "yes", $ROOT contains the DEBUG build and
352 328 $ROOT-nd contains the non-DEBUG build.
353 -.LP
354 -For OpenSolaris deliveries (\fB\-O\fR), $ROOT-closed contains a parallel
355 -proto area containing the DEBUG build of just usr/closed components, and
356 -$ROOT-nd-closed contains the non-DEBUG equivalent.
357 329 .RE
358 330 .LP
359 331 .B TOOLS_ROOT
360 332 .RS 5
361 333 Root of the tools proto area for the build. The makefiles direct
362 334 installation of tools build products to this area. Unless \fB+t\fR
363 335 is part of $NIGHTLY_OPTIONS, these tools will be used during the
364 336 build.
365 337 .LP
366 338 As built by nightly, this will always contain non-DEBUG objects.
367 339 Therefore, this will always have a -nd suffix, regardless of
368 340 $MULTI_PROTO.
369 341 .RE
370 342 .LP
371 343 .B MACH
372 344 .RS 5
373 345 The instruction set architecture of the build machine as given
374 346 by \fIuname -p\fP, e.g. sparc, i386.
375 347 .RE
376 348 .LP
377 349 .B LOCKNAME
378 350 .RS 5
379 351 The name of the file used to lock out multiple runs of
380 352 .IR nightly .
381 353 This should generally be left to the default setting.
382 354 .RE
383 355 .LP
384 356 .B ATLOG
385 357 .RS 5
386 358 The location of the log directory maintained by
387 359 .IR nightly .
388 360 This should generally be left to the default setting.
389 361 .RE
390 362 .LP
391 363 .B LOGFILE
392 364 .RS 5
393 365 The name of the log file in the $ATLOG directory maintained by
394 366 .IR nightly .
395 367 This should generally be left to the default setting.
396 368 .RE
397 369 .LP
398 370 .B STAFFER
399 371 .RS 5
400 372 The non-root account to use on the build machine for the
401 373 bringover from the clone or parent workspace.
402 374 This may not be the same identify used by the SCM.
403 375 .RE
404 376 .LP
405 377 .B MAILTO
406 378 .RS 5
407 379 The address to be used to send completion e-mail at the end of
408 380 the build (for the \-m option).
409 381 .RE
410 382 .LP
411 383 .B MAILFROM
412 384 .RS 5
413 385 The address to be used for From: in the completion e-mail at the
414 386 end of the build (for the \-m option).
415 387 .RE
416 388 .LP
417 389 .B REF_PROTO_LIST
418 390 .RS 5
419 391 Name of file used with protocmp to compare proto area contents.
420 392 .RE
421 393 .LP
422 394 .B PARENT_ROOT
423 395 .RS 5
424 396 The parent root, which is the destination for copying the proto
425 397 area(s) when using the \-U option.
426 398 .RE
427 399 .LP
428 400 .B PARENT_TOOLS_ROOT
429 401 .RS 5
430 402 The parent tools root, which is the destination for copying the tools
431 403 proto area when using the \-U option.
432 404 .RE
433 405 .LP
434 406 .B RELEASE
435 407 .RS 5
436 408 The release version number to be used; e.g., 5.10.1 (Note: this is set
437 409 in Makefile.master and should not normally be overridden).
438 410 .RE
439 411 .LP
440 412 .B VERSION
441 413 .RS 5
442 414 The version text string to be used; e.g., "onnv:`date '+%Y-%m-%d'`".
443 415 .RE
444 416 .LP
445 417 .B RELEASE_DATE
446 418 .RS 5
447 419 The release date text to be used; e.g., October 2009. If not set in
448 420 your environment file, then this text defaults to the output from
449 421 $(LC_ALL=C date +"%B %Y"); e.g., "October 2009".
450 422 .RE
451 423 .LP
452 424 .B INTERNAL_RELEASE_BUILD
453 425 .RS 5
454 426 See Makefile.master - but it mostly controls id strings. Generally,
455 427 let
456 428 .I nightly
457 429 set this for you.
458 430 .RE
459 431 .LP
460 432 .B RELEASE_BUILD
461 433 .RS 5
462 434 Define this to build a release with a non-DEBUG kernel.
463 435 Generally, let
464 436 .I nightly
465 437 set this for you based on its options.
466 438 .RE
467 439 .LP
468 440 .B PKGARCHIVE
469 441 .RS 5
470 442 The destination for packages. This may be relative to
471 443 $CODEMGR_WS for private packages or relative to $PARENT_WS
472 444 if you have different workspaces for different architectures
473 445 but want one hierarchy of packages.
474 446 .RE
475 447 .LP
476 448 .B MAKEFLAGS
477 449 .RS 5
478 450 Set default flags to make; e.g., -k to build all targets regardless of errors.
479 451 .RE
480 452 .LP
481 453 .B UT_NO_USAGE_TRACKING
482 454 .RS 5
483 455 Disables usage reporting by listed Devpro tools. Otherwise it sends mail
484 456 to some Devpro machine every time the tools are used.
485 457 .RE
486 458 .LP
487 459 .B LINTDIRS
488 460 .RS 5
489 461 Directories to lint with the \-l option.
490 462 .RE
491 463 .LP
492 464 .B BUILD_TOOLS
493 465 .RS 5
494 466 BUILD_TOOLS is the root of all tools including the compilers; e.g.,
495 467 /ws/onnv-tools. It is used by the makefile system, but not nightly.
496 468 .RE
497 469 .LP
498 470 .B ONBLD_TOOLS
499 471 .RS 5
500 472 ONBLD_TOOLS is the root of all the tools that are part of SUNWonbld; e.g.,
501 473 /ws/onnv-tools/onbld. By default, it is derived from
502 474 .BR BUILD_TOOLS .
503 475 It is used by the makefile system, but not nightly.
504 476 .RE
505 477 .LP
506 478 .B SPRO_ROOT
507 479 .RS 5
508 480 The gate-defined default location for the Sun compilers, e.g.
509 481 /ws/onnv-tools/SUNWspro. By default, it is derived from
510 482 .BR BUILD_TOOLS .
511 483 It is used by the makefile system, but not nightly.
512 484 .RE
513 485 .LP
514 486 .B JAVA_ROOT
515 487 .RS 5
516 488 The location for the java compilers for the build, generally /usr/java.
517 489 .RE
518 490 .LP
519 491 .B OPTHOME
520 492 .RS 5
521 493 The gate-defined default location of things formerly in /opt; e.g.,
522 494 /ws/onnv-tools. This is used by nightly, but not the makefiles.
523 495 .RE
524 496 .LP
|
↓ open down ↓ |
158 lines elided |
↑ open up ↑ |
525 497 .B TEAMWARE
526 498 .RS 5
527 499 The gate-defined default location for the Teamware tools; e.g.,
528 500 /ws/onnv-tools/SUNWspro. By default, it is derived from
529 501 .BR OPTHOME .
530 502 This is used by nightly, but not the makefiles. There is no
531 503 corresponding variable for Mercurial or Subversion, which are assumed
532 504 to be installed in the default path.
533 505 .RE
534 506 .LP
535 -.B OPEN_SRCDIR
536 -.RS 5
537 -The open source tree is copied to this directory when simulating an
538 -OpenSolaris build (\fB\-S O\fR). It defaults to $CODEMGR_WS/open_src.
539 -.LP
540 -.RE
541 507 .B ON_CLOSED_BINS
542 508 .RS 5
543 509 OpenSolaris builds do not contain the closed source tree. Instead,
544 510 the developer downloads a closed binaries tree and unpacks it.
545 511 .B ON_CLOSED_BINS
546 512 tells nightly
547 513 where to find these closed binaries, so that it can add them into the
548 514 build.
549 515 .LP
550 516 .RE
551 517 .B ON_CRYPTO_BINS
552 518 .RS 5
553 519 This is the path to a compressed tarball that contains debug
554 520 cryptographic binaries that have been signed to allow execution
555 521 outside of Sun, e.g., $PARENT_WS/packages/$MACH/on-crypto.$MACH.bz2.
556 522 .I nightly
557 523 will automatically adjust the path for non-debug builds. This tarball
558 524 is needed if the closed-source tree is not present. Also, it is
559 525 usually needed when generating OpenSolaris deliverables from a project
560 526 workspace. This is because most projects do not have access to the
561 527 necessary key and certificate that would let them sign their own
562 528 cryptographic binaries.
563 529 .LP
564 530 .RE
565 531 .B CHECK_PATHS
566 532 .RS 5
567 533 Normally, nightly runs the 'checkpaths' script to check for
568 534 discrepancies among the files that list paths to other files, such as
569 535 exception lists and req.flg. Set this flag to 'n' to disable this
570 536 check, which appears in the nightly output as "Check lists of files."
571 537 .RE
572 538 .LP
573 539 .B CHECK_DMAKE
574 540 .RS 5
575 541 Nightly validates that the version of dmake encountered is known to be
|
↓ open down ↓ |
25 lines elided |
↑ open up ↑ |
576 542 safe to use. Set this flag to 'n' to disable this test, allowing any
577 543 version of dmake to be used.
578 544 .RE
579 545 .LP
580 546 .B MULTI_PROTO
581 547 .RS 5
582 548 If "no" (the default),
583 549 .I nightly
584 550 will reuse $ROOT for both the DEBUG and non-DEBUG builds. If "yes",
585 551 the DEBUG build will go in $ROOT and the non-DEBUG build will go in
586 -$ROOT-nd. Other values will be treated as "no". Use of the
587 -.B \-O
588 -flag forces MULTI_PROTO to "yes".
552 +$ROOT-nd. Other values will be treated as "no".
589 553 .RE
590 554 .LP
591 555 .SH NIGHTLY HOOK ENVIRONMENT VARIABLES
592 556 .LP
593 557 Several optional environment variables may specify commands to run at
594 558 various points during the build. Commands specified in the hook
595 559 variable will be run in a subshell; command output will be appended to
596 560 the mail message and log file. If the hook exits with a non-zero
597 561 status, the build is aborted immediately. Environment variables
598 562 defined in the environment file will be available.
599 563 .LP
600 564 .B SYS_PRE_NIGHTLY
601 565 .RS 5
602 566 Run just after the workspace lock is acquired. This is reserved for
603 567 per-build-machine customizations and should be set only in /etc/nightly.conf
604 568 .RE
605 569 .LP
606 570 .B PRE_NIGHTLY
607 571 .RS 5
608 572 Run just after SYS_PRE_NIGHTLY.
609 573 .RE
610 574 .LP
611 575 .B PRE_BRINGOVER
612 576 .RS 5
613 577 Run just before bringover is started; not run if no bringover is done.
614 578 .RE
615 579 .LP
616 580 .B POST_BRINGOVER
617 581 .RS 5
618 582 Run just after bringover completes; not run if no bringover is done.
619 583 .RE
620 584 .LP
621 585 .B POST_NIGHTLY
622 586 .RS 5
623 587 Run after the build completes, with the return status of nightly - one
624 588 of "Completed", "Interrupted", or "Failed" - available in the
625 589 environment variable NIGHTLY_STATUS.
626 590 .RE
627 591 .LP
628 592 .B SYS_POST_NIGHTLY
629 593 .RS 5
630 594 This is reserved for per-build-machine customizations, and runs
631 595 immedately after POST_NIGHTLY.
632 596 .RE
633 597 .LP
634 598 .SH REALMODE ENVIRONMENT VARIABLES
635 599 .LP
636 600 The following environment variables referenced by
637 601 .I nightly
638 602 are only required when the -X option is used.
639 603 .LP
640 604 .RE
641 605 .B IA32_IHV_WS
642 606 .RS 5
643 607 Reference to the IHV workspace containing IHV driver binaries.
644 608 The IHV workspace must be fully built before starting the ON realmode build.
645 609 .LP
646 610 .RE
647 611 .B IA32_IHV_ROOT
648 612 .RS 5
649 613 Reference to the IHV workspace proto area.
650 614 The IHV workspace must be fully built before starting the ON realmode build.
651 615 .LP
652 616 .RE
653 617 .B IA32_IHV_PKGS
654 618 .RS 5
655 619 Reference to the IHV workspace packages. If this is empty or the directory
656 620 is non-existent, then nightly will skip copying the packages.
657 621 .LP
658 622 .RE
659 623 .B IA32_IHV_BINARY_PKGS
660 624 .RS 5
661 625 Reference to binary-only IHV packages. If this is empty or the directory
662 626 is non-existent, then nightly will skip copying the packages.
663 627 .LP
664 628 .RE
665 629 .B SPARC_RM_PKGARCHIVE
666 630 .RS 5
667 631 Destination for sparc realmode package SUNWrmodu.
668 632 Yes, this sparc package really is built on x86.
669 633 .SH FILES
670 634 .LP
671 635 .RS 5
672 636 /etc/nightly.conf
673 637 .RE
674 638 .LP
675 639 If present, nightly executes this file just prior to executing the
676 640 .I env
677 641 file.
678 642 .SH BUILDING THE IHV WORKSPACE
679 643 .LP
680 644 The IHV workspace can be built with
681 645 .I nightly.
682 646 The recommended options are:
683 647 .LP
684 648 .RS 5
685 649 NIGHTLY_OPTIONS="-pmWN"
686 650 .RE
687 651 .LP
688 652 None of the realmode environment variables needed for ON realmode builds
689 653 are required to build the IHV workspace.
690 654 .SH EXAMPLES
691 655 .LP
692 656 Start with the example file in usr/src/tools/env/developer.sh
693 657 (or gatekeeper.sh), copy to myenv and make your changes.
694 658 .LP
695 659 .PD 0
696 660 # grep NIGHTLY_OPTIONS myenv
697 661 .LP
698 662 NIGHTLY_OPTIONS="-ACrlapDm"
699 663 .LP
700 664 export NIGHTLY_OPTIONS
701 665 .LP
702 666 # /opt/onbld/bin/nightly -i myenv
703 667 .PD
704 668 .LP
705 669 .SH SEE ALSO
706 670 .BR bldenv (1)
|
↓ open down ↓ |
108 lines elided |
↑ open up ↑ |
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX