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