###############################################################################
#
# Makefile for X Consolidation packages
#
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# Software is furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice (including the next
# paragraph) shall be included in all copies or substantial portions of the
# Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
# LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
# FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
# DEALINGS IN THE SOFTWARE.
#
###############################################################################
# Please read the comments in it and the accompanying README in ON for many
# details omitted here.
# Major differences in the X implementation:
# - X only supports building one repo, not redist + extra
# - X only supports building packages on the same platform as the binaries,
# no cross-platform packaging
# - X has no bfu legacy to deal with
# - ON has all manifests in one directory, X splits into current & legacy
### Include common definitions
# We don't yet support building packages cross-architecture, but would
# need this if we ever did. (See "Cross platform packaging notes" in
# Map X makefile names to the ones used in the rules copied from ON
# More to be updated if we ever decide to support building cross-platform
# Map the V=1 style of enabling more verbose build messages used in the
#
# You can enable verbose output with either V=1 or PKGDEBUG=""
PKGDEBUG_V_0 = @
# Commands used in rules copied from ON
#
# To suppress package dependency generation on any system, regardless
# of how it was installed, set SUPPRESSPKGDEP=true in the build
# environment.
#
SUPPRESSPKGDEP= false
#
# The packages directory will contain the processed manifests as
# direct build targets and subdirectories for package metadata extracted
# incidentally during manifest processing.
#
# Nothing underneath $(PDIR) should ever be managed by SCM.
#
$(PDIR):
mkdir -p $@
#
# subset of packages, override this on the command line or in the
# build environment and then reference (implicitly or explicitly) the all
# or install targets.
#
#
# Track the synthetic manifests separately so we can properly express
# build rules and dependencies. The synthetic and real packages use
# different sets of transforms and macros for pkgmogrify.
#
# Special manifest for exceptions to pass to pkglint & validate_pkg
# Manifests are in either manifests or legacy directory - merge in $(PDIR)
$(ALL_MANIFESTS): $(PDIR)
### Additional metadata generation
$(PROTOMETA)/%/:
# Generate default copyright notice for packages without contents
-e 's/^# //' -e 'p' -e 'q' -e'}' $< > $@
# This should eventually move into pkg publication
$(FONT_ATTRS): $(FONT_METADATA)
@print "## Generating font metadata in $(@F)"
### Manifest mogrification
# RELEASE = uname -r for the target release
# The PKGVERS_BRANCH is determined by the values in the Makefile.buildnum
# PSARC 2012/240 for package version scheme
# Generate pkgmogrify transform file with correct build version info in
# Build number is derived from last nv_XXX tag in hg log
@print "## Substituting build info in versions transformation template"
# Set variables used by pkgmogrify
# These are the macros that may be used in package manifests
# Most upstream packages provide specific version numbers instead of using
# the default of $(OSPKGVERS)
# Some use $(X11PKGVERS) to refer to the X11 katamari version since they
# bundle together components from multiple upstream packages with individual
# version numbers
# Base URL for ARC cases used in opensolaris.arc_url metadata
# 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)"
esac ; \
$(PKGMOG_DEFINES:%=-D %) -O $(@) \
# List of all packages we build, used in open source code release zip files
$(TOP)/pkglist.txt:
@print "## Generating pkglist.txt"
### Dependency detection
# Package manifest containing list of packages to use in dependency
'PLATFORM=i86hvm' \
'PLATFORM=i86pc' \
'PLATFORM=i86xpv' \
'ISALIST=amd64' \
'ISALIST=i386'
'PLATFORM=sun4u' \
'PLATFORM=sun4v' \
'ISALIST=sparcv9' \
'ISALIST=sparc'
@print "## Generating dependencies for $(<F)"
$(PKGROOT) > $(@); \
else \
fi
### 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
# stay in sync.
@print "## Generating package list for dependency resolution"
# This rule resolves dependencies across all manifests for packages
# currently delivering files.
print "## Suppressing dependency resolution"; \
for p in $(DEP_CURRENT_PKGS:%.dep=%); do \
done; \
else \
print "## Resolving dependencies"; \
$(PKGDEP_VERBOSE_FLAG) -e $(PKGDEP_RESOLVE_LIST) \
-m $(DEP_CURRENT_PKGS) ; \
fi
# Post-processing of manifests after dependency resolution
$(PKGDEBUG)if [[ -s $< ]] ; then \
-O $@ -P $(@:%.res=%.synth) $< $(POST_TRANSFORMS) ; \
else \
$(CP) $< $@ ; \
fi
# Generate info for synthetic manifests
-O $(@) -P $(@:%.res=%.synth.sed) \
### 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"
@$(RM) $@
if [[ -s $$p.res ]]; then \
CHECK_PKGS="$$p.res $${CHECK_PKGS}"; \
fi; \
done; \
if [[ -n "$${CHECK_PKGS}" ]]; then \
fi ; \
return 1; \
fi
@$(TOUCH) $@
### Repo setup
# Default in developer builds is "xnv-devel"
# X RE cronjob build scripts override to "xnv-nightly"
# Initialize the empty on-disk repositories
$(PKGDEST):
@print "## Initializing $(@F)"
### Package publication to repo
fi; \
$(TOUCH) $(@)
$(PUB_SYNTH_PKGS): $(SYNTH_LICENSES)
### Repo finalization
@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
# lint runs.
#
lint:
$(PKGLINT_REFERENCE_REPO:%=-r %) \
### Overall rules
#
# rules to validate proto area against manifests, and check for safe
# file permission modes
#
# Automatically exclude all pkg-config uninstalled.pc files, since those
# should never be packaged
@print "## Checking for manifests not in pkgfmt expected form"
@print ""
# 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"
# Nothing to do for "make source", but avoid error when run at top-level
source:
@true