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