Makefile revision 1360
749N/A############################################################################### 749N/A# Makefile for X Consolidation packages 749N/A# Copyright (c) 2010, 2013, Oracle and/or its affiliates. All rights reserved. 749N/A# Permission is hereby granted, free of charge, to any person obtaining a 749N/A# copy of this software and associated documentation files (the "Software"), 749N/A# to deal in the Software without restriction, including without limitation 749N/A# the rights to use, copy, modify, merge, publish, distribute, sublicense, 749N/A# and/or sell copies of the Software, and to permit persons to whom the 749N/A# Software is furnished to do so, subject to the following conditions: 749N/A# The above copyright notice and this permission notice (including the next 749N/A# paragraph) shall be included in all copies or substantial portions of the 749N/A# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 749N/A# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 749N/A# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL 749N/A# THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 749N/A# LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING 749N/A# FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER 749N/A# DEALINGS IN THE SOFTWARE. 749N/A############################################################################### 749N/A# Please read the comments in it and the accompanying README in ON for many 749N/A# Major differences in the X implementation: 749N/A# - X only supports building one repo, not redist + extra 749N/A# - X only supports building packages on the same platform as the binaries, 749N/A# no cross-platform packaging 749N/A# - X has no bfu legacy to deal with 749N/A# - ON has all manifests in one directory, X splits into current & legacy 749N/A### Include common definitions 749N/A# We don't yet support building packages cross-architecture, but would 749N/A# need this if we ever did. (See "Cross platform packaging notes" in 749N/A# Map X makefile names to the ones used in the rules copied from ON 749N/A# More to be updated if we ever decide to support building cross-platform 749N/A# Map the V=1 style of enabling more verbose build messages used in the 749N/A# You can enable verbose output with either V=1 or PKGDEBUG="" 749N/A# Commands used in rules copied from ON 749N/A# To suppress package dependency generation on any system, regardless 749N/A# of how it was installed, set SUPPRESSPKGDEP=true in the build 749N/A# The packages directory will contain the processed manifests as 749N/A# direct build targets and subdirectories for package metadata extracted 749N/A# incidentally during manifest processing. 749N/A# Nothing underneath $(PDIR) should ever be managed by SCM. 749N/A# By default, PKGS will list all manifests. To build and/or publish a 749N/A# subset of packages, override this on the command line or in the 749N/A# build environment and then reference (implicitly or explicitly) the all 749N/A# Track the synthetic manifests separately so we can properly express 749N/A# build rules and dependencies. The synthetic and real packages use 749N/A# different sets of transforms and macros for pkgmogrify. 749N/A# Special manifest for exceptions to pass to pkglint & validate_pkg 749N/A# Manifests are in either manifests or legacy directory - merge in $(PDIR) 749N/A### Additional metadata generation 749N/A# Generate default copyright notice for packages without contents 749N/A -e
's/^# //' -e
'p' -e
'q' -e
'}' $< > $@
749N/A# This should eventually move into pkg publication 749N/A @
print "## Generating font metadata in $(@F)" 749N/A### Manifest mogrification 749N/A# RELEASE = uname -r for the target release 749N/A# Generate pkgmogrify transform file with correct build version info in 749N/A# Build number is derived from last nv_XXX tag in hg log 749N/A @
print "## Substituting build info in versions transformation template" 749N/A# Set variables used by pkgmogrify 749N/A# These are the macros that may be used in package manifests 749N/A# Most upstream packages provide specific version numbers instead of using 749N/A# the default of $(OSPKGVERS) 749N/A# Some use $(X11PKGVERS) to refer to the X11 katamari version since they 749N/A# bundle together components from multiple upstream packages with individual 749N/A# Platform specific choices 749N/A# Architecture specific directory names 749N/A# automake version needed for build dependencies 749N/A# Default transformations to apply 749N/A# Additional transforms for specific types of packages 749N/A# Combine & uniq metadata & license attributes generated during build 749N/A @
print "## Gathering metadata from build for $(@F)" 749N/A### Dependency detection 749N/A# Package manifest containing list of packages to use in dependency 749N/A @
print "## Generating dependencies for $(<F)" 749N/A @
print "## Skipping dependency generation for $(@F:%.dep=%)" 749N/A### Dependency resolution 749N/A# Root of pkg image to use for dependency resolution 749N/A# Normally / on the machine used to build the binaries 749N/A# File listing packages to consider in dependency resolution. 749N/A# Automatically generated from the developer package to ensure they 749N/A @
print "## Generating package list for dependency resolution" 749N/A# This rule resolves dependencies across all manifests for packages 749N/A# currently delivering files. 749N/A print "## Suppressing dependency resolution"; \
749N/A print "## Resolving dependencies"; \
749N/A @
print "## Skipping dependency generation for $(@F:%.dep.res=%)" 749N/A# Post-processing of manifests after dependency resolution 749N/A @
print "## Post-processing manifest for $(@F:%.res=%)" 749N/A# Generate info for synthetic manifests 749N/A @
print "## Gathering package lists for synthetic package $(@F:%.res=%)" 749N/A### pkglint checking (pre-publication) 749N/A# This rule runs pkglint across all manifests to be published. 749N/A# We require that packages be free from lint ERRORs before allowing them 749N/A# to be published. Lint WARNINGs are acceptable (though unpleasant) 749N/A# The list of packages is the list of packages that did not resolve to 749N/A# 0-byte files, $CHECK_PKGS 749N/A @
print "## Checking packages" 749N/A if [[ -n
"$${CHECK_PKGS}" ]];
then \
749N/A# Default in developer builds is "xnv-devel" 749N/A# X RE cronjob build scripts override to "xnv-nightly" 749N/A# Initialize the empty on-disk repositories 749N/A @
print "## Initializing $(@F)" 749N/A### Package publication to repo 749N/A print "## Publishing $(@F:%.pub=%) to proto repository"; \
749N/A @
print "## Creating repository metadata" 749N/A### pkglint checking (post-publication) 749N/A# Perform a pkglint run on the published repositories. We remove package 749N/A# version information from the lint output so that it is comparable across 749N/A# rules to validate proto area against manifests, and check for safe 749N/A# should never be packaged 749N/A @
print "## Checking for manifests not in pkgfmt expected form" 749N/A# Instead of fixing all the upstream packages to follow our permission rules 749N/A# just fix the proto area to match our rules 749N/A @
print "## Fixing proto area permissions"