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