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