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