| README.tools (34c989574817eca41f72a5f02c848e51cfef32f0) | README.tools (b84bdc3085e48b1603b754ed1848a58043acfa86) |
|---|---|
| 1# 2# CDDL HEADER START 3# 4# The contents of this file are subject to the terms of the 5# Common Development and Distribution License (the "License"). 6# You may not use this file except in compliance with the License. 7# 8# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE --- 18 unchanged lines hidden (view full) --- 27This directory contains the tools used to do a full build of the 28OS/Net workspace. They usually live in the /opt/onbld directory on build 29machines. From here, 'make install' will build and install the tools 30in $ROOT/opt/onbld. If you like, 'make pkg' will build the SUNWonbld 31package in $(PKGARCHIVE). Installing that package will populate the 32/opt/onbld directory, and create a root account for building called 'gk', 33which uses csh and has a home directory of /opt/onbld/gk. You can 34use this account to do full builds with 'nightly'. You don't have to, | 1# 2# CDDL HEADER START 3# 4# The contents of this file are subject to the terms of the 5# Common Development and Distribution License (the "License"). 6# You may not use this file except in compliance with the License. 7# 8# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE --- 18 unchanged lines hidden (view full) --- 27This directory contains the tools used to do a full build of the 28OS/Net workspace. They usually live in the /opt/onbld directory on build 29machines. From here, 'make install' will build and install the tools 30in $ROOT/opt/onbld. If you like, 'make pkg' will build the SUNWonbld 31package in $(PKGARCHIVE). Installing that package will populate the 32/opt/onbld directory, and create a root account for building called 'gk', 33which uses csh and has a home directory of /opt/onbld/gk. You can 34use this account to do full builds with 'nightly'. You don't have to, |
| 35you just need to be root do a full build, but the 'gk' account has 36the path setup properly, contains a .make.machines file for pmake, 37and the .login attempts to set up for dmake (if it ever works). | 35but the 'gk' account has the path setup properly, has a .make.machines 36file for dmake, and has a .login that sets up for dmake. |
| 38 39Layout of /opt/onbld 40-------------------- 41 42/opt/onbld/etc/abi 43 contains Solaris ABI database (ABI_*.db) and exceptions 44 for ABI Auditing tool (intf_check). 45 --- 218 unchanged lines hidden (view full) --- 264 2651. Find an environment file that might do what you want to do. If you're just 266 a developer wanting to do a full build in a child of the gate, copy the 267 'developer' environment file to a new name (private to you and/or the 268 work being done in this workspace, to avoid collisions with others). Then 269 edit the file and tailor it to your workspace. Remember that this file 270 is a shell script, so it can do more than set environment variables. 271 | 37 38Layout of /opt/onbld 39-------------------- 40 41/opt/onbld/etc/abi 42 contains Solaris ABI database (ABI_*.db) and exceptions 43 for ABI Auditing tool (intf_check). 44 --- 218 unchanged lines hidden (view full) --- 263 2641. Find an environment file that might do what you want to do. If you're just 265 a developer wanting to do a full build in a child of the gate, copy the 266 'developer' environment file to a new name (private to you and/or the 267 work being done in this workspace, to avoid collisions with others). Then 268 edit the file and tailor it to your workspace. Remember that this file 269 is a shell script, so it can do more than set environment variables. 270 |
| 2722. Login as 'gk' (or root, but your PATH and .make.machines for pmake will | 2712. Login as 'gk' (or root, but your PATH and .make.machines for dmake will |
| 273 not be right). Run 'nightly' and give it your environment file as an 274 option. 'nightly' will first look for your environment file in 275 /opt/onbld/env, and if it's not there then it will look for it as an 276 absolute or relative path. Some people put their environment files in 277 their workspace to keep them close. 278 2793. When 'nightly' is complete, it will send a summary of what happened to 280 $MAILTO. Usually, the less info in the mail the better. If you have failures, --- 15 unchanged lines hidden --- | 272 not be right). Run 'nightly' and give it your environment file as an 273 option. 'nightly' will first look for your environment file in 274 /opt/onbld/env, and if it's not there then it will look for it as an 275 absolute or relative path. Some people put their environment files in 276 their workspace to keep them close. 277 2783. When 'nightly' is complete, it will send a summary of what happened to 279 $MAILTO. Usually, the less info in the mail the better. If you have failures, --- 15 unchanged lines hidden --- |