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) 2010, Oracle and/or its affiliates. All rights reserved. 24# Copyright 2015, OmniTI Computer Consulting, Inc. All rights reserved. 25# Copyright 2015 Igor Kozhukhov <ikozhukhov@gmail.com> 26# Copyright 2016 RackTop Systems. 27# Copyright 2018 OmniOS Community Edition (OmniOSce) Association. 28# 29 30include $(SRC)/Makefile.master 31include $(SRC)/Makefile.buildnum 32 33# 34# Make sure we're getting a consistent execution environment for the 35# embedded scripts. 36# 37SHELL= /usr/bin/ksh93 38 39# 40# To suppress package dependency generation on any system, regardless 41# of how it was installed, set SUPPRESSPKGDEP=true in the build 42# environment. 43# 44SUPPRESSPKGDEP= false 45 46# 47# Comment this line out or set "PKGDEBUG=" in your build environment 48# to get more verbose output from the make processes in usr/src/pkg 49# 50PKGDEBUG= @ 51 52# 53# Cross platform packaging notes 54# 55# By default, we package the proto area from the same architecture as 56# the packaging build. In other words, if you're running nightly or 57# bldenv on an x86 platform, it will take objects from the x86 proto 58# area and use them to create x86 repositories. 59# 60# If you want to create repositories for an architecture that's 61# different from $(uname -p), you do so by setting PKGMACH in your 62# build environment. 63# 64# For this to work correctly, the following must all happen: 65# 66# 1. You need the desired proto area, which you can get either by 67# doing a gatekeeper-style build with the -U option to 68# nightly(1), or by using rsync. If you don't do this, you will 69# get packaging failures building all packages, because pkgsend 70# is unable to find the required binaries. 71# 2. You need the desired tools proto area, which you can get in the 72# same ways as the normal proto area. If you don't do this, you 73# will get packaging failures building onbld, because pkgsend is 74# unable to find the tools binaries. 75# 3. The remainder of this Makefile should never refer directly to 76# $(MACH). Instead, $(PKGMACH) should be used whenever an 77# architecture-specific path or token is needed. If this is done 78# incorrectly, then packaging will fail, and you will see the 79# value of $(uname -p) instead of the value of $(PKGMACH) in the 80# commands that fail. 81# 4. Each time a rule in this Makefile invokes $(MAKE), it should 82# pass PKGMACH=$(PKGMACH) explicitly on the command line. If 83# this is done incorrectly, then packaging will fail, and you 84# will see the value of $(uname -p) instead of the value of 85# $(PKGMACH) in the commands that fail. 86# 87# Refer also to the convenience targets defined later in this 88# Makefile. 89# 90PKGMACH= $(MACH) 91 92# 93# ROOT, TOOLS_PROTO, and PKGARCHIVE should be set by nightly or 94# bldenv. These macros translate them into terms of $PKGMACH, instead 95# of $ARCH. 96# 97PKGROOT.cmd= print $(ROOT) | sed -e s:/root_$(MACH):/root_$(PKGMACH): 98PKGROOT= $(PKGROOT.cmd:sh) 99TOOLSROOT.cmd= print $(TOOLS_PROTO) | sed -e s:/root_$(MACH):/root_$(PKGMACH): 100TOOLSROOT= $(TOOLSROOT.cmd:sh) 101PKGDEST.cmd= print $(PKGARCHIVE) | sed -e s:/$(MACH)/:/$(PKGMACH)/: 102PKGDEST= $(PKGDEST.cmd:sh) 103 104EXCEPTIONS= packaging 105 106PKGMOGRIFY= pkgmogrify 107 108# 109# Always build the redistributable repository, but only build the 110# nonredistributable bits if we have access to closed source. 111# 112# Some objects that result from the closed build are still 113# redistributable, and should be packaged as part of an open-only 114# build. Access to those objects is provided via the closed-bins 115# tarball. See usr/src/tools/scripts/bindrop.sh for details. 116# 117REPOS= redist 118 119# 120# The packages directory will contain the processed manifests as 121# direct build targets and subdirectories for package metadata extracted 122# incidentally during manifest processing. 123# 124# Nothing underneath $(PDIR) should ever be managed by SCM. 125# 126PDIR= packages.$(PKGMACH) 127 128# 129# The tools proto must be specified for dependency generation. 130# Publication from the tools proto area is managed in the 131# publication rule. 132# 133$(PDIR)/developer-build-onbld.dep:= PKGROOT= $(TOOLSROOT) 134 135PKGPUBLISHER= $(PKGPUBLISHER_REDIST) 136 137# 138# To get these defaults, manifests should simply refer to $(PKGVERS). 139# 140PKGVERS_COMPONENT= 0.$(RELEASE) 141PKGVERS_BUILTON= $(RELEASE) 142PKGVERS_BRANCH= 0.$(ONNV_BUILDNUM) 143PKGVERS= $(PKGVERS_COMPONENT),$(PKGVERS_BUILTON)-$(PKGVERS_BRANCH) 144 145# 146# The ARCH32 and ARCH64 macros are used in the manifests to express 147# architecture-specific subdirectories in the installation paths 148# for isaexec'd commands. 149# 150# We can't simply use $(MACH32) and $(MACH64) here, because they're 151# only defined for the build architecture. To do cross-platform 152# packaging, we need both values. 153# 154i386_ARCH32= i86 155sparc_ARCH32= sparcv7 156i386_ARCH64= amd64 157sparc_ARCH64= sparcv9 158 159# 160# macros and transforms needed by pkgmogrify 161# 162# If you append to this list using target-specific assignments (:=), 163# be very careful that the targets are of the form $(PDIR)/pkgname. If 164# you use a higher level target, or a package list, you'll trigger a 165# complete reprocessing of all manifests because they'll fail command 166# dependency checking. 167# 168PM_TRANSFORMS= common_actions publish restart_fmri facets defaults \ 169 extract_metadata 170PM_INC= transforms manifests 171 172JAVA_7_ONLY= 173JAVA_8_ONLY= 174$(BLD_JAVA_6)JAVA_7_ONLY=$(POUND_SIGN) 175$(BLD_JAVA_6)JAVA_8_ONLY=$(POUND_SIGN) 176$(BLD_JAVA_8)JAVA_7_ONLY=$(POUND_SIGN) 177$(JAVA_7_ONLY)JAVA_8_ONLY=$(POUND_SIGN) 178 179PKGMOG_DEFINES= \ 180 i386_ONLY=$(POUND_SIGN) \ 181 sparc_ONLY=$(POUND_SIGN) \ 182 $(PKGMACH)_ONLY= \ 183 ARCH=$(PKGMACH) \ 184 ARCH32=$($(PKGMACH)_ARCH32) \ 185 ARCH64=$($(PKGMACH)_ARCH64) \ 186 PKGVERS_COMPONENT=$(PKGVERS_COMPONENT) \ 187 PKGVERS_BUILTON=$(PKGVERS_BUILTON) \ 188 PKGVERS_BRANCH=$(PKGVERS_BRANCH) \ 189 PKGVERS=$(PKGVERS) \ 190 PERL_ARCH=$(PERL_ARCH) \ 191 PERL_ARCH64=$(PERL_ARCH64) \ 192 PERL_VERSION=$(PERL_VERSION) \ 193 PERL_PKGVERS=$(PERL_PKGVERS) \ 194 BUILDPERL32=$(BUILDPERL32) \ 195 BUILDPERL64=$(BUILDPERL64) \ 196 PYTHON_VERSION=$(PYTHON_VERSION) \ 197 PYTHON3_VERSION=$(PYTHON3_VERSION) \ 198 PYTHON_PKGVERS=$(PYTHON_PKGVERS) \ 199 PYTHON3_PKGVERS=$(PYTHON3_PKGVERS) \ 200 python2_ONLY=$(BUILDPY2) \ 201 python3_ONLY=$(BUILDPY3) \ 202 python2tools_ONLY=$(BUILDPY2TOOLS) \ 203 python3tools_ONLY=$(BUILDPY3TOOLS) \ 204 JAVA_8_ONLY=$(JAVA_8_ONLY) \ 205 JAVA_7_ONLY=$(JAVA_7_ONLY) 206 207PKGDEP_TOKENS_i386= \ 208 'PLATFORM=i86hvm' \ 209 'PLATFORM=i86pc' \ 210 'PLATFORM=i86xpv' \ 211 'ISALIST=amd64' \ 212 'ISALIST=i386' 213PKGDEP_TOKENS_sparc= \ 214 'PLATFORM=sun4u' \ 215 'PLATFORM=sun4v' \ 216 'ISALIST=sparcv9' \ 217 'ISALIST=sparc' 218PKGDEP_TOKENS= $(PKGDEP_TOKENS_$(PKGMACH)) 219 220# 221# The package lists are generated with $(PKGDEP_TYPE) as their 222# dependency types, so that they can be included by either an 223# incorporation or a group package. 224# 225$(PDIR)/osnet-redist.mog := PKGDEP_TYPE= require 226$(PDIR)/osnet-incorporation.mog:= PKGDEP_TYPE= incorporate 227 228PKGDEP_INCORP= \ 229 depend fmri=consolidation/osnet/osnet-incorporation type=require 230 231# 232# All packaging build products should go into $(PDIR), so they don't 233# need to be included separately in CLOBBERFILES. 234# 235CLOBBERFILES= $(PDIR) proto_list_$(PKGMACH) install-$(PKGMACH).out \ 236 license-list 237 238# 239# By default, PKGS will list all manifests. To build and/or publish a 240# subset of packages, override this on the command line or in the 241# build environment and then reference (implicitly or explicitly) the all 242# or install targets. 243# 244# We want some manifests to optionally build based on environment options, so 245# those are excluded when generating the list of manifests and added back in if 246# necessary. We also want a relatively easy way to add files to the list of 247# manifests given special treatment. Add any other special ones to the 248# SPECIAL_MANIFESTS variable. It can contain wildcards in regexp form, i.e. 249# SUNW.* as one useful example. 250# 251SPECIAL_MANIFESTS = system-library-python-.* 252LIST_MANIFESTS_CMD = (cd manifests ; /usr/bin/ls -1 *.mf |\ 253 $(SED) $(SPECIAL_MANIFESTS:%=-e '/^%$$/d') ) 254MANIFESTS = $(LIST_MANIFESTS_CMD:sh) 255 256# Conditionally add back python modules 257$(BUILDPY2) MANIFESTS += \ 258 system-library-python-libbe-2.mf \ 259 system-library-python-solaris-2.mf \ 260 system-library-python-zfs-2.mf 261$(BUILDPY3) MANIFESTS += \ 262 system-library-python-libbe-3.mf \ 263 system-library-python-solaris-3.mf \ 264 system-library-python-zfs-3.mf 265 266PKGS= $(MANIFESTS:%.mf=%) 267DEP_PKGS= $(PKGS:%=$(PDIR)/%.dep) 268PROC_PKGS= $(PKGS:%=$(PDIR)/%.mog) 269 270# 271# Track the synthetic manifests separately so we can properly express 272# build rules and dependencies. The synthetic and real packages use 273# different sets of transforms and macros for pkgmogrify. 274# 275SYNTH_PKGS= osnet-incorporation osnet-redist 276DEP_SYNTH_PKGS= $(SYNTH_PKGS:%=$(PDIR)/%.dep) 277PROC_SYNTH_PKGS= $(SYNTH_PKGS:%=$(PDIR)/%.mog) 278 279# 280# Root of pkg image to use for dependency resolution 281# Normally / on the machine used to build the binaries 282# 283PKGDEP_RESOLVE_IMAGE = / 284 285# 286# For each package, we determine the target repository based on 287# manifest-embedded metadata. Because we make that determination on 288# the fly, the publication target cannot be expressed as a 289# subdirectory inside the unknown-by-the-makefile target repository. 290# 291# In order to limit the target set to real files in known locations, 292# we use a ".pub" file in $(PDIR) for each processed manifest, regardless 293# of content or target repository. 294# 295PUB_PKGS= $(SYNTH_PKGS:%=$(PDIR)/%.pub) $(PKGS:%=$(PDIR)/%.pub) 296 297# 298# Any given repository- and status-specific package list may be empty, 299# but we can only determine that dynamically, so we always generate all 300# lists for each repository we're building. 301# 302# The meanings of each package status are as follows: 303# 304# PKGSTAT meaning 305# ---------- ---------------------------------------------------- 306# noincorp Do not include in incorporation or group package 307# obsolete Include in incorporation, but not group package 308# renamed Include in incorporation, but not group package 309# current Include in incorporation and group package 310# 311# Since the semantics of the "noincorp" package status dictate that 312# such packages are not included in the incorporation or group packages, 313# there is no need to build noincorp package lists. 314# 315PKGLISTS= \ 316 $(REPOS:%=$(PDIR)/packages.%.current) \ 317 $(REPOS:%=$(PDIR)/packages.%.renamed) \ 318 $(REPOS:%=$(PDIR)/packages.%.obsolete) 319 320.KEEP_STATE: 321 322.PARALLEL: $(PKGS) $(PROC_PKGS) $(DEP_PKGS) \ 323 $(PROC_SYNTH_PKGS) $(DEP_SYNTH_PKGS) $(PUB_PKGS) 324 325# 326# For a single manifest, the dependency chain looks like this: 327# 328# raw manifest (mypkg.mf) 329# | 330# | use pkgmogrify to process raw manifest 331# | 332# processed manifest (mypkg.mog) 333# | 334# * | use pkgdepend generate to generate dependencies 335# | 336# manifest with TBD dependencies (mypkg.dep) 337# | 338# % | use pkgdepend resolve to resolve dependencies 339# | 340# manifest with dependencies resolved (mypkg.res) 341# | 342# | use pkgsend to publish the package 343# | 344# placeholder to indicate successful publication (mypkg.pub) 345# 346# * This may be suppressed via SUPPRESSPKGDEP. The resulting 347# packages will install correctly, but care must be taken to 348# install all dependencies, because pkg will not have the input 349# it needs to determine this automatically. 350# 351# % This is included in this diagram to make the picture complete, but 352# this is a point of synchronization in the build process. 353# Dependency resolution is actually done once on the entire set of 354# manifests, not on a per-package basis. 355# 356# The full dependency chain for generating everything that needs to be 357# published, without actually publishing it, looks like this: 358# 359# processed synthetic packages 360# | | 361# package lists synthetic package manifests 362# | 363# processed real packages 364# | | 365# package dir real package manifests 366# 367# Here, each item is a set of real or synthetic packages. For this 368# portion of the build, no reference is made to the proto area. It is 369# therefore suitable for the "all" target, as opposed to "install." 370# 371# Since each of these steps is expressed explicitly, "all" need only 372# depend on the head of the chain. 373# 374# From the end of manifest processing, the publication dependency 375# chain looks like this: 376# 377# repository metadata (catalogs and search indices) 378# | 379# | pkgrepo refresh 380# | 381# published packages 382# | | 383# | | pkgsend publish 384# | | 385# repositories resolved dependencies 386# | | 387# pkgsend | | pkgdepend resolve 388# create-repository | 389# | generated dependencies 390# repo directories | 391# | pkgdepend 392# | 393# processed manifests 394# 395 396ALL_TARGETS= $(PROC_SYNTH_PKGS) proto_list_$(PKGMACH) 397 398all: $(ALL_TARGETS) 399 400# 401# This will build the directory to contain the processed manifests 402# and the metadata symlinks. 403# 404$(PDIR): 405 @print "Creating $(@)" 406 $(PKGDEBUG)$(INS.dir) 407 408# 409# This rule resolves dependencies across all published manifests. 410# 411# We shouldn't have to ignore the error from pkgdepend, but until 412# 16012 and its dependencies are resolved, pkgdepend will always exit 413# with an error. 414# 415$(PDIR)/gendeps: $(DEP_SYNTH_PKGS) $(DEP_PKGS) 416 -$(PKGDEBUG)if [ "$(SUPPRESSPKGDEP)" = "true" ]; then \ 417 print "Suppressing dependency resolution"; \ 418 for p in $(DEP_PKGS:%.dep=%); do \ 419 $(CP) $$p.dep $$p.res; \ 420 done; \ 421 else \ 422 print "Resolving dependencies"; \ 423 pkgdepend -R $(PKGDEP_RESOLVE_IMAGE) resolve \ 424 -m $(DEP_SYNTH_PKGS) $(DEP_PKGS); \ 425 for p in $(DEP_SYNTH_PKGS:%.dep=%) $(DEP_PKGS:%.dep=%); do \ 426 if [ "$$(print $$p.metadata.*)" = \ 427 "$$(print $$p.metadata.noincorp.*)" ]; \ 428 then \ 429 print "Removing dependency versions from $$p"; \ 430 $(PKGMOGRIFY) $(PKGMOG_VERBOSE) \ 431 -O $$p.res -I transforms \ 432 strip_versions $$p.dep.res; \ 433 $(RM) $$p.dep.res; \ 434 else \ 435 $(MV) $$p.dep.res $$p.res; \ 436 fi; \ 437 done; \ 438 fi 439 $(PKGDEBUG)$(TOUCH) $(@) 440 441install: $(ALL_TARGETS) repository-metadata 442 443repository-metadata: publish_pkgs 444 $(PKGDEBUG)for r in $(REPOS); do \ 445 pkgrepo refresh -s $(PKGDEST)/repo.$$r; \ 446 done 447 448# 449# Since we create zero-length processed manifests for a graceful abort 450# from pkgmogrify, we need to detect that here and make no effort to 451# publish the package. 452# 453# For all other packages, we publish them regardless of status. We 454# derive the target repository as a component of the metadata-derived 455# symlink for each package. 456# 457publish_pkgs: $(REPOS:%=$(PKGDEST)/repo.%) $(PDIR)/gendeps .WAIT $(PUB_PKGS) 458 459# 460# Before publishing, we want to pull the license files from $CODEMGR_WS 461# into the proto area. This allows us to NOT pass $SRC (or 462# $CODEMGR_WS) as a basedir for publication. 463# 464$(PUB_PKGS): stage-licenses 465 466# 467# Initialize the empty on-disk repositories 468# 469$(REPOS:%=$(PKGDEST)/repo.%): 470 @print "Initializing $(@F)" 471 $(PKGDEBUG)$(INS.dir) 472 $(PKGDEBUG)pkgsend -s file://$(@) create-repository \ 473 --set-property publisher.prefix=$(PKGPUBLISHER) 474 475# 476# rule to process real manifests 477# 478# To allow redistributability and package status to change, we must 479# remove not only the actual build target (the processed manifest), but 480# also the incidental ones (the metadata-derived symlinks). 481# 482# If pkgmogrify exits cleanly but fails to create the specified output 483# file, it means that it encountered an abort directive. That means 484# that this package should not be published for this particular build 485# environment. Since we can't prune such packages from $(PKGS) 486# retroactively, we need to create an empty target file to keep make 487# from trying to rebuild it every time. For these empty targets, we 488# do not create metadata symlinks. 489# 490# Automatic dependency resolution to files is also done at this phase of 491# processing. The skipped packages are skipped due to existing bugs 492# in pkgdepend. 493# 494# The incorporation dependency is tricky: it needs to go into all 495# current and renamed manifests (ie all incorporated packages), but we 496# don't know which those are until after we run pkgmogrify. So 497# instead of expressing it as a transform, we tack it on ex post facto. 498# 499# Implementation notes: 500# 501# - The first $(RM) must not match other manifests, or we'll run into 502# race conditions with parallel manifest processing. 503# 504# - The make macros [ie $(MACRO)] are evaluated when the makefile is 505# read in, and will result in a fixed, macro-expanded rule for each 506# target enumerated in $(PROC_PKGS). 507# 508# - The shell variables (ie $$VAR) are assigned on the fly, as the rule 509# is executed. The results may only be referenced in the shell in 510# which they are assigned, so from the perspective of make, all code 511# that needs these variables needs to be part of the same line of 512# code. Hence the use of command separators and line continuation 513# characters. 514# 515# - The extract_metadata transforms are designed to spit out shell 516# variable assignments to stdout. Those are published to the 517# .vars temporary files, and then used as input to the eval 518# statement. This is done in stages specifically so that pkgmogrify 519# can signal failure if the manifest has a syntactic or other error. 520# The eval statement should begin with the default values, and the 521# output from pkgmogrify (if any) should be in the form of a 522# variable assignment to override those defaults. 523# 524# - When this rule completes execution, it must leave an updated 525# target file ($@) in place, or make will reprocess the package 526# every time it encounters it as a dependency. Hence the "touch" 527# statement to ensure that the target is created, even when 528# pkgmogrify encounters an abort in the publish transforms. 529# 530 531.SUFFIXES: .mf .mog .dep .res .pub 532 533$(PDIR)/%.mog: manifests/%.mf 534 @print "Processing manifest $(<F)" 535 @env PKGFMT_OUTPUT=v1 pkgfmt -c $< 536 $(PKGDEBUG)$(RM) $(@) $(@:%.mog=%) $(@:%.mog=%.nodepend) \ 537 $(@:%.mog=%.lics) $(PDIR)/$(@F:%.mog=%).metadata.* $(@).vars 538 $(PKGDEBUG)$(PKGMOGRIFY) $(PKGMOG_VERBOSE) $(PM_INC:%= -I %) \ 539 $(PKGMOG_DEFINES:%=-D %) -P $(@).vars -O $(@) \ 540 $(<) $(PM_TRANSFORMS) 541 $(PKGDEBUG)eval REPO=redist PKGSTAT=current NODEPEND=$(SUPPRESSPKGDEP) \ 542 `$(CAT) -s $(@).vars`; \ 543 if [ -f $(@) ]; then \ 544 if [ "$$NODEPEND" != "false" ]; then \ 545 $(TOUCH) $(@:%.mog=%.nodepend); \ 546 fi; \ 547 $(LN) -s $(@F) \ 548 $(PDIR)/$(@F:%.mog=%).metadata.$$PKGSTAT.$$REPO; \ 549 if [ \( "$$PKGSTAT" = "current" \) -o \ 550 \( "$$PKGSTAT" = "renamed" \) ]; \ 551 then print $(PKGDEP_INCORP) >> $(@); \ 552 fi; \ 553 print $$LICS > $(@:%.mog=%.lics); \ 554 else \ 555 $(TOUCH) $(@) $(@:%.mog=%.lics); \ 556 fi 557 $(PKGDEBUG)$(RM) $(@).vars 558 559$(PDIR)/%.dep: $(PDIR)/%.mog 560 @print "Generating dependencies for $(<F)" 561 $(PKGDEBUG)$(RM) $(@) 562 $(PKGDEBUG)if [ ! -f $(@:%.dep=%.nodepend) ]; then \ 563 pkgdepend generate -m $(PKGDEP_TOKENS:%=-D %) $(<) \ 564 $(PKGROOT) > $(@); \ 565 else \ 566 $(CP) $(<) $(@); \ 567 fi 568 569# 570# The full chain implies that there should be a .dep.res suffix rule, 571# but dependency generation is done on a set of manifests, rather than 572# on a per-manifest basis. Instead, see the gendeps rule above. 573# 574 575$(PDIR)/%.pub: $(PDIR)/%.res 576 $(PKGDEBUG)m=$$(basename $(@:%.pub=%).metadata.*); \ 577 r=$${m#$(@F:%.pub=%.metadata.)+(?).}; \ 578 if [ -s $(<) ]; then \ 579 print "Publishing $(@F:%.pub=%) to $$r repository"; \ 580 pkgsend -s file://$(PKGDEST)/repo.$$r publish \ 581 -d $(PKGROOT) -d $(TOOLSROOT) \ 582 -d license_files -d $(PKGROOT)/licenses \ 583 --fmri-in-manifest --no-index --no-catalog $(<) \ 584 > /dev/null; \ 585 fi; \ 586 $(TOUCH) $(@); 587 588# 589# rule to build the synthetic manifests 590# 591# This rule necessarily has PKGDEP_TYPE that changes according to 592# the specific synthetic manifest. Rather than escape command 593# dependency checking for the real manifest processing, or failing to 594# express the (indirect) dependency of synthetic manifests on real 595# manifests, we simply split this rule out from the one above. 596# 597# The implementation notes from the previous rule are applicable 598# here, too. 599# 600$(PROC_SYNTH_PKGS): $(PKGLISTS) $$(@F:%.mog=%.mf) 601 @print "Processing synthetic manifest $(@F:%.mog=%.mf)" 602 $(PKGDEBUG)$(RM) $(@) $(PDIR)/$(@F:%.mog=%).metadata.* $(@).vars 603 $(PKGDEBUG)$(PKGMOGRIFY) $(PKGMOG_VERBOSE) -I transforms -I $(PDIR) \ 604 $(PKGMOG_DEFINES:%=-D %) -D PKGDEP_TYPE=$(PKGDEP_TYPE) \ 605 -P $(@).vars -O $(@) $(@F:%.mog=%.mf) \ 606 $(PM_TRANSFORMS) synthetic 607 $(PKGDEBUG)eval REPO=redist PKGSTAT=current `$(CAT) -s $(@).vars`; \ 608 if [ -f $(@) ]; then \ 609 $(LN) -s $(@F) \ 610 $(PDIR)/$(@F:%.mog=%).metadata.$$PKGSTAT.$$REPO; \ 611 else \ 612 $(TOUCH) $(@); \ 613 fi 614 $(PKGDEBUG)$(RM) $(@).vars 615 616$(DEP_SYNTH_PKGS): $$(@:%.dep=%.mog) 617 @print "Skipping dependency generation for $(@F:%.dep=%)" 618 $(PKGDEBUG)$(CP) $(@:%.dep=%.mog) $(@) 619 620clean: 621 622clobber: clean 623 $(RM) -r $(CLOBBERFILES) 624 625# 626# This rule assumes that all links in the $PKGSTAT directories 627# point to valid manifests, and will fail the make run if one 628# does not contain an fmri. 629# 630# We do this in the BEGIN action instead of using pattern matching 631# because we expect the fmri to be at or near the first line of each input 632# file, and this way lets us avoid reading the rest of the file after we 633# find what we need. 634# 635# We keep track of a failure to locate an fmri, so we can fail the 636# make run, but we still attempt to process each package in the 637# repo/pkgstat-specific subdir, in hopes of maybe giving some 638# additional useful info. 639# 640# The protolist is used for bfu archive creation, which may be invoked 641# interactively by the user. Both protolist and PKGLISTS targets 642# depend on $(PROC_PKGS), but protolist builds them recursively. 643# To avoid collisions, we insert protolist into the dependency chain 644# here. This has two somewhat subtle benefits: it allows bfu archive 645# creation to work correctly, even when -a was not part of NIGHTLY_OPTIONS, 646# and it ensures that a protolist file here will always correspond to the 647# contents of the processed manifests, which can vary depending on build 648# environment. 649# 650$(PKGLISTS): $(PROC_PKGS) 651 $(PKGDEBUG)sdotr=$(@F:packages.%=%); \ 652 r=$${sdotr%.+(?)}; s=$${sdotr#+(?).}; \ 653 print "Generating $$r $$s package list"; \ 654 $(RM) $(@); $(TOUCH) $(@); \ 655 $(AWK) 'BEGIN { \ 656 if (ARGC < 2) { \ 657 exit; \ 658 } \ 659 retcode = 0; \ 660 for (i = 1; i < ARGC; i++) { \ 661 do { \ 662 e = getline f < ARGV[i]; \ 663 } while ((e == 1) && (f !~ /name=pkg.fmri/)); \ 664 close(ARGV[i]); \ 665 if (e == 1) { \ 666 l = split(f, a, "="); \ 667 print "depend fmri=" a[l], \ 668 "type=$$(PKGDEP_TYPE)"; \ 669 } else { \ 670 print "no fmri in " ARGV[i] >> "/dev/stderr"; \ 671 retcode = 2; \ 672 } \ 673 } \ 674 exit retcode; \ 675 }' `find $(PDIR) -type l -a \( $(PKGS:%=-name %.metadata.$$s.$$r -o) \ 676 -name NOSUCHFILE \)` >> $(@) 677 678# 679# rules to validate proto area against manifests, check for safe 680# file permission modes, and generate a faux proto list 681# 682# For the check targets, the dependencies on $(PROC_PKGS) is specified 683# as a subordinate make process in order to suppress output. 684# 685makesilent: 686 @$(MAKE) -e $(PROC_PKGS) PKGMACH=$(PKGMACH) \ 687 SUPPRESSPKGDEP=$(SUPPRESSPKGDEP) > /dev/null 688 689# 690# The .lics files were created during pkgmogrification, and list the 691# set of licenses to pull from $SRC for each package. Because 692# licenses may be duplicated between packages, we uniquify them as 693# well as aggregating them here. 694# 695license-list: makesilent 696 $(PKGDEBUG)( for l in `cat $(PROC_PKGS:%.mog=%.lics)`; \ 697 do print $$l; done ) | sort -u > $@ 698 699# 700# Staging the license and description files in the proto area allows 701# us to do proper unreferenced file checking of both license and 702# description files without blanket exceptions, and to pull license 703# content without reference to $CODEMGR_WS during publication. 704# 705stage-licenses: license-list FRC 706 $(PKGDEBUG)$(MAKE) -e -f Makefile.lic \ 707 PKGDEBUG=$(PKGDEBUG) LICROOT=$(PKGROOT)/licenses \ 708 `$(AWK) '{ \ 709 print "$(PKGROOT)/licenses/" $$0; \ 710 print "$(PKGROOT)/licenses/" $$0 ".descrip"; \ 711 }' license-list` > /dev/null; 712 713protocmp: makesilent 714 @validate_pkg -a $(PKGMACH) -v \ 715 $(EXCEPTIONS:%=-e $(CODEMGR_WS)/exception_lists/%) \ 716 -m $(PDIR) -p $(PKGROOT) -p $(TOOLSROOT) 717 718pmodes: makesilent 719 @validate_pkg -a $(PKGMACH) -M -m $(PDIR) \ 720 -e $(CODEMGR_WS)/exception_lists/pmodes 721 722check: protocmp pmodes 723 724protolist: proto_list_$(PKGMACH) 725 726proto_list_$(PKGMACH): $(PROC_PKGS) 727 @validate_pkg -a $(PKGMACH) -L -m $(PDIR) > $(@) 728 729$(PROC_PKGS): $(PDIR) 730 731# 732# This is a convenience target to allow package names to function as 733# build targets. Generally, using it is only useful when iterating on 734# development of a manifest. 735# 736# When processing a manifest, use the basename (without extension) of 737# the package. When publishing, use the basename with a ".pub" 738# extension. 739# 740# Other than during manifest development, the preferred usage is to 741# avoid these targets and override PKGS on the make command line and 742# use the provided all and install targets. 743# 744$(PKGS) $(SYNTH_PKGS): $(PDIR)/$$(@:%=%.mog) 745 746$(PKGS:%=%.pub) $(SYNTH_PKGS:%=%.pub): $(PDIR)/$$(@) 747 748# 749# This is a convenience target to resolve dependencies without publishing 750# packages. 751# 752gendeps: $(PDIR)/gendeps 753 754# 755# These are convenience targets for cross-platform packaging. If you 756# want to build any of "the normal" targets for a different 757# architecture, simply use "arch/target" as your build target. 758# 759# Since the most common use case for this is "install," the architecture 760# specific install targets have been further abbreviated to elide "/install." 761# 762i386/% sparc/%: 763 $(MAKE) -e $(@F) PKGMACH=$(@D) SUPPRESSPKGDEP=$(SUPPRESSPKGDEP) 764 765i386 sparc: $$(@)/install 766 767FRC: 768