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 packages for PIT/RE (-p) 36# checks for new interfaces in libraries (-A) 37# runs 'make check' (-C) 38# runs lint in usr/src (-l plus the LINTDIRS variable) 39# sends mail on completion (-m and the MAILTO variable) 40# updates the protolist in the parent for children to compare with (-u) 41# updates the proto area in the parent when done (-U) 42# checks for changes in ELF runpaths (-r) 43# checks for changes in unreferenced files (-f) 44# 45NIGHTLY_OPTIONS="-ADClmpuUrf"; export NIGHTLY_OPTIONS 46 47# This is a variable for the rest of the script - GATE doesn't matter to 48# nightly itself 49GATE=onnv-gate; export GATE 50 51# CODEMGR_WS - where is your workspace at (or what should nightly name it) 52# there is only one definition here, which assumes all the gate build machines 53# (sparc and x86) are set up the same. But remember, this is a script, so 54# you _could_ look at $MACH or `uname -n` and set these variables differently. 55CODEMGR_WS="/builds/$GATE"; export CODEMGR_WS 56 57# PARENT_WS is used to determine the parent of this workspace. This is 58# for the options that deal with the parent workspace (such as where the 59# proto area will go). 60# 61# If you use this, it must be local (or nfs): nightly cannot copy 62# over ssh or http. 63PARENT_WS="/ws/$GATE"; export PARENT_WS 64 65# CLONE_WS is the workspace nightly should do a bringover from. 66CLONE_WS="ssh://anonhg@onnv.sfbay.sun.com//export/onnv-clone"; export CLONE_WS 67 68# CLOSED_CLONE_WS is the workspace from which nightly will acquire the 69# usr/closed tree. 70CLOSED_CLONE_WS="${CLONE_WS}/usr/closed" 71export CLOSED_CLONE_WS 72 73# The bringover, if any, is done as STAFFER. 74# Set STAFFER to your own login as gatekeeper or integration engineer. 75# The point is to use group "staff" and avoid referencing the parent 76# workspace as root. 77# Some scripts optionally send mail messages to MAILTO. 78# 79STAFFER=nobody; export STAFFER 80MAILTO=$STAFFER; export MAILTO 81 82# The project (see project(4)) under which to run this build. If not 83# specified, the build is simply run in a new task in the current project. 84BUILD_PROJECT=; export BUILD_PROJECT 85 86# You should not need to change the next three lines 87ATLOG="$CODEMGR_WS/log"; export ATLOG 88LOGFILE="$ATLOG/nightly.log"; export LOGFILE 89MACH=`uname -p`; export MACH 90 91# When the -A flag is specified, and ELF_DATA_BASELINE_DIR is defined, 92# the ELF interface description file resulting from the build is compared 93# to that from the specified directory. This ensures that our object 94# versioning evolves in a backward compatible manner. 95# 96# You should not need to change this unless you wish to use locally cached 97# baseline files. If you use this, it must be local (or nfs): nightly cannot 98# copy over ssh or http. 99# 100ELF_DATA_BASELINE_DIR="/ws/onnv-gate/usr/src/ELF-data-baseline.$MACH"; export ELF_DATA_BASELINE_DIR 101 102# This is usually just needed if the closed tree is missing, or when 103# building a project gate with the -O (cap oh) flag. 104# ON_CRYPTO_BINS="$PARENT_WS/packages/$MACH/on-crypto.$MACH.tar.bz2" 105# export ON_CRYPTO_BINS 106 107# REF_PROTO_LIST - for comparing the list of stuff in your proto area 108# with. Generally this should be left alone, since you want to see differences 109# between todays build and yesterdays. 110# 111REF_PROTO_LIST=$PARENT_WS/usr/src/proto_list_${MACH}; export REF_PROTO_LIST 112 113# 114# build environment variables, including version info for mcs, motd, 115# motd, uname and boot messages. Mostly you shouldn't change this except 116# when the release slips (nah) or when starting a new release. 117# 118ROOT="$CODEMGR_WS/proto/root_${MACH}"; export ROOT 119SRC="$CODEMGR_WS/usr/src"; export SRC 120VERSION="$GATE"; export VERSION 121 122# 123# the RELEASE and RELEASE_DATE variables are set in Makefile.master; 124# there might be special reasons to override them here, but that 125# should not be the case in general 126# 127# RELEASE="5.10.1"; export RELEASE 128# RELEASE_DATE="October 2007"; export RELEASE_DATE 129 130# proto area in parent for optionally depositing a copy of headers and 131# libraries corresponding to the protolibs target 132# 133PARENT_ROOT=$PARENT_WS/proto/root_$MACH; export PARENT_ROOT 134PARENT_TOOLS_ROOT=$PARENT_WS/usr/src/tools/proto/root_$MACH-nd; export PARENT_TOOLS_ROOT 135 136# 137# Package creation variables. You probably shouldn't change these, 138# either. 139# 140# PKGARCHIVE determines where repositories will be created. 141# 142# PKGPUBLISHER* control the publisher settings for those repositories. 143# 144PKGARCHIVE="${PARENT_WS}/packages/${MACH}/nightly"; export PKGARCHIVE 145# PKGPUBLISHER_REDIST="on-nightly"; export PKGPUBLISHER_REDIST 146# PKGPUBLISHER_NONREDIST="on-extra"; export PKGPUBLISHER_NONREDIST 147 148 149# we want make to do as much as it can, just in case there's more than 150# one problem. This is especially important with the gate, since multiple 151# unrelated broken things can be integrated. 152MAKEFLAGS=k; export MAKEFLAGS 153 154# Magic variable to prevent the devpro compilers/teamware from sending 155# mail back to devpro on every use. 156UT_NO_USAGE_TRACKING="1"; export UT_NO_USAGE_TRACKING 157 158# Build tools - don't set these unless you know what you're doing. These 159# variables allows you to get the compilers and onbld files locally or 160# through cachefs. Set BUILD_TOOLS to pull everything from one location. 161# Alternately, you can set ONBLD_TOOLS to where you keep the contents of 162# SUNWonbld and SPRO_ROOT to where you keep the compilers. 163# 164#BUILD_TOOLS=/opt; export BUILD_TOOLS 165#ONBLD_TOOLS=/opt/onbld; export ONBLD_TOOLS 166#SPRO_ROOT=/opt/SUNspro; export SPRO_ROOT 167 168# This goes along with lint - it is a series of the form "A [y|n]" which 169# means "go to directory A and run 'make lint'" Then mail me (y) the 170# difference in the lint output. 'y' should only be used if the area you're 171# linting is actually lint clean or you'll get lots of mail. 172# You shouldn't need to change this though. 173#LINTDIRS="$SRC y"; export LINTDIRS 174 175# 176# Reference to IA32 IHV workspace, proto area and packages 177# 178#IA32_IHV_WS=/ws/${GATE}-ihv; export IA32_IHV_WS 179#IA32_IHV_ROOT=$IA32_IHV_WS/proto/root_i386; export IA32_IHV_ROOT 180#IA32_IHV_PKGS=$IA32_IHV_WS/packages/i386/nightly; export IA32_IHV_PKGS 181 182# 183# Reference to binary-only IA32 IHV packages 184# 185#IA32_IHV_BINARY_PKGS=/ws/${GATE}-ihv-bin 186#export IA32_IHV_BINARY_PKGS 187 188# Set this flag to 'n' to disable the use of 'checkpaths'. The default, 189# if the 'N' option is not specified, is to run this test. 190#CHECK_PATHS=y 191 192# Set this flag to 'y' to enable the use of elfsigncmp to validate the 193# output of elfsign. Doing so requires that 't' be set in NIGHTLY_OPTIONS. 194# The default is to not verify them. 195#VERIFY_ELFSIGN=n 196 197# BRINGOVER_FILES is the list of files nightly passes to bringover. 198# If not set the default is "usr", but it can be used for bringing 199# over deleted_files or other nifty directories. 200#BRINGOVER_FILES="usr deleted_files" 201 202# POST_NIGHTLY can be any command to be run at the end of nightly. See 203# nightly(1) for interactions between environment variables and this command. 204#POST_NIGHTLY= 205