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 9# or http://www.opensolaris.org/os/licensing. 10# See the License for the specific language governing permissions 11# and limitations under the License. 12# 13# When distributing Covered Code, include this CDDL HEADER in each 14# file and include the License file at usr/src/OPENSOLARIS.LICENSE. 15# If applicable, add the following below this CDDL HEADER, with the 16# fields enclosed by brackets "[]" replaced with your own identifying 17# information: Portions Copyright [yyyy] [name of copyright owner] 18# 19# CDDL HEADER END 20# 21 22# 23# Copyright (c) 1999, 2010, Oracle and/or its affiliates. All rights reserved. 24# 25 26# Configuration variables for the runtime environment of the nightly 27# build script and other tools for construction and packaging of releases. 28# This script is sourced by 'nightly' and 'bldenv' to set up the environment 29# for the build. This example is suitable for building a gate, 30# which will contain the resulting packages and archives (builds of the gate 31# are done in children and then the resulting archives, packages, and proto 32# area are put into the parent for everyone to use). It is based off 33# the onnv release. It sets NIGHTLY_OPTIONS to make nightly do: 34# DEBUG and non-DEBUG builds (-D) 35# creates cpio archives for bfu (-a) 36# creates packages for PIT/RE (-p) 37# checks for new interfaces in libraries (-A) 38# runs 'make check' (-C) 39# runs lint in usr/src (-l plus the LINTDIRS variable) 40# sends mail on completion (-m and the MAILTO variable) 41# updates the protolist in the parent for children to compare with (-u) 42# updates the proto area in the parent when done (-U) 43# checks for changes in ELF runpaths (-r) 44# checks for changes in unreferenced files (-f) 45# 46NIGHTLY_OPTIONS="-aADClmpuUrf"; export NIGHTLY_OPTIONS 47 48# This is a variable for the rest of the script - GATE doesn't matter to 49# nightly itself 50GATE=onnv-gate; export GATE 51 52# CODEMGR_WS - where is your workspace at (or what should nightly name it) 53# there is only one definition here, which assumes all the gate build machines 54# (sparc and x86) are set up the same. But remember, this is a script, so 55# you _could_ look at $MACH or `uname -n` and set these variables differently. 56CODEMGR_WS="/builds/$GATE"; export CODEMGR_WS 57 58# PARENT_WS is used to determine the parent of this workspace. This is 59# for the options that deal with the parent workspace (such as where the 60# proto area will go). 61# 62# If you use this, it must be local (or nfs): nightly cannot copy 63# over ssh or http. 64PARENT_WS="/ws/$GATE"; export PARENT_WS 65 66# CLONE_WS is the workspace nightly should do a bringover from. 67CLONE_WS="ssh://anonhg@onnv.sfbay.sun.com//export/onnv-clone"; export CLONE_WS 68 69# CLOSED_CLONE_WS is the workspace from which nightly will acquire the 70# usr/closed tree. 71CLOSED_CLONE_WS="${CLONE_WS}/usr/closed" 72export CLOSED_CLONE_WS 73 74# This flag controls whether to build the closed source. If 75# undefined, nightly(1) and bldenv(1) will set it according to whether 76# the closed source tree is present. CLOSED_IS_PRESENT="no" means not 77# building the closed sources. 78# CLOSED_IS_PRESENT="yes"; export CLOSED_IS_PRESENT 79 80# The bringover, if any, is done as STAFFER. 81# Set STAFFER to your own login as gatekeeper or integration engineer. 82# The point is to use group "staff" and avoid referencing the parent 83# workspace as root. 84# Some scripts optionally send mail messages to MAILTO. 85# 86STAFFER=nobody; export STAFFER 87MAILTO=$STAFFER; export MAILTO 88 89# The project (see project(4)) under which to run this build. If not 90# specified, the build is simply run in a new task in the current project. 91BUILD_PROJECT=; export BUILD_PROJECT 92 93# You should not need to change the next four lines 94LOCKNAME="`basename $CODEMGR_WS`_nightly.lock"; export LOCKNAME 95ATLOG="$CODEMGR_WS/log"; export ATLOG 96LOGFILE="$ATLOG/nightly.log"; export LOGFILE 97MACH=`uname -p`; export MACH 98 99# When the -A flag is specified, and ELF_DATA_BASELINE_DIR is defined, 100# the ELF interface description file resulting from the build is compared 101# to that from the specified directory. This ensures that our object 102# versioning evolves in a backward compatible manner. 103# 104# You should not need to change this unless you wish to use locally cached 105# baseline files. If you use this, it must be local (or nfs): nightly cannot 106# copy over ssh or http. 107# 108ELF_DATA_BASELINE_DIR="/ws/onnv-gate/usr/src/ELF-data-baseline.$MACH"; export ELF_DATA_BASELINE_DIR 109 110# This is usually just needed if the closed tree is missing, or when 111# building a project gate with the -O (cap oh) flag. 112# ON_CRYPTO_BINS="$PARENT_WS/packages/$MACH/on-crypto.$MACH.tar.bz2" 113# export ON_CRYPTO_BINS 114 115# REF_PROTO_LIST - for comparing the list of stuff in your proto area 116# with. Generally this should be left alone, since you want to see differences 117# between todays build and yesterdays. 118# 119REF_PROTO_LIST=$PARENT_WS/usr/src/proto_list_${MACH}; export REF_PROTO_LIST 120 121# where cpio archives of the OS are placed. Usually this should be left 122# alone too. Here they don't go in the build workspace, but in the parent. 123# Since this is done as root, the build machine needs root acces to 124# the parent over NFS. 125CPIODIR="${PARENT_WS}/archives/${MACH}/nightly"; export CPIODIR 126 127# 128# build environment variables, including version info for mcs, motd, 129# motd, uname and boot messages. Mostly you shouldn't change this except 130# when the release slips (nah) or when starting a new release. 131# 132ROOT="$CODEMGR_WS/proto/root_${MACH}"; export ROOT 133SRC="$CODEMGR_WS/usr/src"; export SRC 134VERSION="$GATE"; export VERSION 135 136# 137# the RELEASE and RELEASE_DATE variables are set in Makefile.master; 138# there might be special reasons to override them here, but that 139# should not be the case in general 140# 141# RELEASE="5.10.1"; export RELEASE 142# RELEASE_DATE="October 2007"; export RELEASE_DATE 143 144# proto area in parent for optionally depositing a copy of headers and 145# libraries corresponding to the protolibs target 146# 147PARENT_ROOT=$PARENT_WS/proto/root_$MACH; export PARENT_ROOT 148PARENT_TOOLS_ROOT=$PARENT_WS/usr/src/tools/proto/root_$MACH-nd; export PARENT_TOOLS_ROOT 149 150# 151# Package creation variables. You probably shouldn't change these, 152# either. 153# 154# PKGARCHIVE determines where repositories will be created. 155# 156# PKGPUBLISHER* control the publisher settings for those repositories. 157# 158PKGARCHIVE="${PARENT_WS}/packages/${MACH}/nightly"; export PKGARCHIVE 159# PKGPUBLISHER_REDIST="on-nightly"; export PKGPUBLISHER_REDIST 160# PKGPUBLISHER_NONREDIST="on-extra"; export PKGPUBLISHER_NONREDIST 161 162 163# we want make to do as much as it can, just in case there's more than 164# one problem. This is especially important with the gate, since multiple 165# unrelated broken things can be integrated. 166MAKEFLAGS=k; export MAKEFLAGS 167 168# Magic variable to prevent the devpro compilers/teamware from sending 169# mail back to devpro on every use. 170UT_NO_USAGE_TRACKING="1"; export UT_NO_USAGE_TRACKING 171 172# Build tools - don't set these unless you know what you're doing. These 173# variables allows you to get the compilers and onbld files locally or 174# through cachefs. Set BUILD_TOOLS to pull everything from one location. 175# Alternately, you can set ONBLD_TOOLS to where you keep the contents of 176# SUNWonbld and SPRO_ROOT to where you keep the compilers. 177# 178#BUILD_TOOLS=/opt; export BUILD_TOOLS 179#ONBLD_TOOLS=/opt/onbld; export ONBLD_TOOLS 180#SPRO_ROOT=/opt/SUNspro; export SPRO_ROOT 181 182# This goes along with lint - it is a series of the form "A [y|n]" which 183# means "go to directory A and run 'make lint'" Then mail me (y) the 184# difference in the lint output. 'y' should only be used if the area you're 185# linting is actually lint clean or you'll get lots of mail. 186# You shouldn't need to change this though. 187#LINTDIRS="$SRC y"; export LINTDIRS 188 189# 190# Reference to IA32 IHV workspace, proto area and packages 191# 192#IA32_IHV_WS=/ws/${GATE}-ihv; export IA32_IHV_WS 193#IA32_IHV_ROOT=$IA32_IHV_WS/proto/root_i386; export IA32_IHV_ROOT 194#IA32_IHV_PKGS=$IA32_IHV_WS/packages/i386/nightly; export IA32_IHV_PKGS 195 196# 197# Reference to binary-only IA32 IHV packages 198# 199#IA32_IHV_BINARY_PKGS=/ws/${GATE}-ihv-bin 200#export IA32_IHV_BINARY_PKGS 201 202# Set this flag to 'n' to disable the automatic validation of the dmake 203# version in use. The default is to check it. 204#CHECK_DMAKE=y 205 206# Set this flag to 'n' to disable the use of 'checkpaths'. The default, 207# if the 'N' option is not specified, is to run this test. 208#CHECK_PATHS=y 209 210# Set this flag to 'y' to enable the use of elfsigncmp to validate the 211# output of elfsign. Doing so requires that 't' be set in NIGHTLY_OPTIONS. 212# The default is to not verify them. 213#VERIFY_ELFSIGN=n 214 215# BRINGOVER_FILES is the list of files nightly passes to bringover. 216# If not set the default is "usr", but it can be used for bringing 217# over deleted_files or other nifty directories. 218#BRINGOVER_FILES="usr deleted_files" 219 220# POST_NIGHTLY can be any command to be run at the end of nightly. See 221# nightly(1) for interactions between environment variables and this command. 222#POST_NIGHTLY= 223