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