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