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.
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.
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]
23 # Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved.
26 include $(SRC
)/Makefile.master
27 include $(SRC
)/Makefile.buildnum
30 # Make sure we're getting a consistent execution environment for the
36 # To suppress package dependency generation on any system, regardless
37 # of how it was installed, set SUPPRESSPKGDEP=true in the build
43 # Comment this line out or set "PKGDEBUG=" in your build environment
44 # to get more verbose output from the make processes in usr/src/pkg
49 # Cross platform packaging notes
51 # By default, we package the proto area from the same architecture as
52 # the packaging build. In other words, if you're running nightly or
53 # bldenv on an x86 platform, it will take objects from the x86 proto
54 # area and use them to create x86 repositories.
56 # If you want to create repositories for an architecture that's
57 # different from $(uname -p), you do so by setting PKGMACH in your
60 # For this to work correctly, the following must all happen:
62 # 1. You need the desired proto area, which you can get either by
63 # doing a gatekeeper-style build with the -U option to
64 # nightly(1), or by using rsync. If you don't do this, you will
65 # get packaging failures building all packages, because pkgsend
66 # is unable to find the required binaries.
67 # 2. You need the desired tools proto area, which you can get in the
68 # same ways as the normal proto area. If you don't do this, you
69 # will get packaging failures building onbld, because pkgsend is
70 # unable to find the tools binaries.
71 # 3. The remainder of this Makefile should never refer directly to
72 # $(MACH). Instead, $(PKGMACH) should be used whenever an
73 # architecture-specific path or token is needed. If this is done
74 # incorrectly, then packaging will fail, and you will see the
75 # value of $(uname -p) instead of the value of $(PKGMACH) in the
77 # 4. Each time a rule in this Makefile invokes $(MAKE), it should
78 # pass PKGMACH=$(PKGMACH) explicitly on the command line. If
79 # this is done incorrectly, then packaging will fail, and you
80 # will see the value of $(uname -p) instead of the value of
81 # $(PKGMACH) in the commands that fail.
83 # Refer also to the convenience targets defined later in this
89 # ROOT, TOOLS_PROTO, and PKGARCHIVE should be set by nightly or
90 # bldenv. These macros translate them into terms of $PKGMACH, instead
93 PKGROOT.cmd
= print $(ROOT
) | sed
-e s
:/root_
$(MACH
):/root_
$(PKGMACH
):
94 PKGROOT
= $(PKGROOT.cmd
:sh
)
95 TOOLSROOT.cmd
= print $(TOOLS_PROTO
) | sed
-e s
:/root_
$(MACH
):/root_
$(PKGMACH
):
96 TOOLSROOT
= $(TOOLSROOT.cmd
:sh
)
97 PKGDEST.cmd
= print $(PKGARCHIVE
) | sed
-e s
:/$(MACH
)/:/$(PKGMACH
)/:
98 PKGDEST
= $(PKGDEST.cmd
:sh
)
100 EXCEPTIONS
= packaging
102 PKGMOGRIFY
= pkgmogrify
105 # Always build the redistributable repository, but only build the
106 # nonredistributable bits if we have access to closed source.
108 # Some objects that result from the closed build are still
109 # redistributable, and should be packaged as part of an open-only
110 # build. Access to those objects is provided via the closed-bins
111 # tarball. See usr/src/tools/scripts/bindrop.sh for details.
116 # The packages directory will contain the processed manifests as
117 # direct build targets and subdirectories for package metadata extracted
118 # incidentally during manifest processing.
120 # Nothing underneath $(PDIR) should ever be managed by SCM.
122 PDIR
= packages.
$(PKGMACH
)
125 # The tools proto must be specified for dependency generation.
126 # Publication from the tools proto area is managed in the
129 $(PDIR
)/developer-build-onbld.dep
:= PKGROOT
= $(TOOLSROOT
)
131 PKGPUBLISHER
= $(PKGPUBLISHER_REDIST
)
134 # To get these defaults, manifests should simply refer to $(PKGVERS).
136 PKGVERS_COMPONENT
= 0.
$(RELEASE
)
137 PKGVERS_BUILTON
= $(RELEASE
)
138 PKGVERS_BRANCH
= 0.
$(ONNV_BUILDNUM
)
139 PKGVERS
= $(PKGVERS_COMPONENT
),$(PKGVERS_BUILTON
)-$(PKGVERS_BRANCH
)
142 # The ARCH32 and ARCH64 macros are used in the manifests to express
143 # architecture-specific subdirectories in the installation paths
144 # for isaexec'd commands.
146 # We can't simply use $(MACH32) and $(MACH64) here, because they're
147 # only defined for the build architecture. To do cross-platform
148 # packaging, we need both values.
151 sparc_ARCH32
= sparcv7
153 sparc_ARCH64
= sparcv9
156 # macros and transforms needed by pkgmogrify
158 # If you append to this list using target-specific assignments (:=),
159 # be very careful that the targets are of the form $(PDIR)/pkgname. If
160 # you use a higher level target, or a package list, you'll trigger a
161 # complete reprocessing of all manifests because they'll fail command
162 # dependency checking.
164 PM_TRANSFORMS
= common_actions publish restart_fmri facets defaults \
166 PM_INC
= transforms manifests
169 i386_ONLY
=$(POUND_SIGN
) \
170 sparc_ONLY
=$(POUND_SIGN
) \
173 ARCH32
=$($(PKGMACH
)_ARCH32
) \
174 ARCH64
=$($(PKGMACH
)_ARCH64
) \
175 PKGVERS_COMPONENT
=$(PKGVERS_COMPONENT
) \
176 PKGVERS_BUILTON
=$(PKGVERS_BUILTON
) \
177 PKGVERS_BRANCH
=$(PKGVERS_BRANCH
) \
179 PERL_VERSION
=$(PERL_VERSION
) \
180 PERL_PKGVERS
=$(PERL_PKGVERS
)
182 PKGDEP_TOKENS_i386
= \
188 PKGDEP_TOKENS_sparc
= \
193 PKGDEP_TOKENS
= $(PKGDEP_TOKENS_
$(PKGMACH
))
196 # The package lists are generated with $(PKGDEP_TYPE) as their
197 # dependency types, so that they can be included by either an
198 # incorporation or a group package.
200 $(PDIR
)/osnet-redist.mog
:= PKGDEP_TYPE
= require
201 $(PDIR
)/osnet-incorporation.mog
:= PKGDEP_TYPE
= incorporate
204 depend fmri
=consolidation
/osnet
/osnet-incorporation type
=require
207 # All packaging build products should go into $(PDIR), so they don't
208 # need to be included separately in CLOBBERFILES.
210 CLOBBERFILES
= $(PDIR
) proto_list_
$(PKGMACH
) install-
$(PKGMACH
).out \
214 # By default, PKGS will list all manifests. To build and/or publish a
215 # subset of packages, override this on the command line or in the
216 # build environment and then reference (implicitly or explicitly) the all
217 # or install targets.
219 MANIFESTS
:sh
= (cd manifests
; print *.mf
)
220 PKGS
= $(MANIFESTS
:%.mf
=%)
221 DEP_PKGS
= $(PKGS
:%=$(PDIR
)/%.dep
)
222 PROC_PKGS
= $(PKGS
:%=$(PDIR
)/%.mog
)
225 # Track the synthetic manifests separately so we can properly express
226 # build rules and dependencies. The synthetic and real packages use
227 # different sets of transforms and macros for pkgmogrify.
229 SYNTH_PKGS
= osnet-incorporation osnet-redist
230 DEP_SYNTH_PKGS
= $(SYNTH_PKGS
:%=$(PDIR
)/%.dep
)
231 PROC_SYNTH_PKGS
= $(SYNTH_PKGS
:%=$(PDIR
)/%.mog
)
234 # Root of pkg image to use for dependency resolution
235 # Normally / on the machine used to build the binaries
237 PKGDEP_RESOLVE_IMAGE
= /
240 # For each package, we determine the target repository based on
241 # manifest-embedded metadata. Because we make that determination on
242 # the fly, the publication target cannot be expressed as a
243 # subdirectory inside the unknown-by-the-makefile target repository.
245 # In order to limit the target set to real files in known locations,
246 # we use a ".pub" file in $(PDIR) for each processed manifest, regardless
247 # of content or target repository.
249 PUB_PKGS
= $(SYNTH_PKGS
:%=$(PDIR
)/%.pub
) $(PKGS
:%=$(PDIR
)/%.pub
)
252 # Any given repository- and status-specific package list may be empty,
253 # but we can only determine that dynamically, so we always generate all
254 # lists for each repository we're building.
256 # The meanings of each package status are as follows:
259 # ---------- ----------------------------------------------------
260 # noincorp Do not include in incorporation or group package
261 # obsolete Include in incorporation, but not group package
262 # renamed Include in incorporation, but not group package
263 # current Include in incorporation and group package
265 # Since the semantics of the "noincorp" package status dictate that
266 # such packages are not included in the incorporation or group packages,
267 # there is no need to build noincorp package lists.
270 $(REPOS
:%=$(PDIR
)/packages.
%.current
) \
271 $(REPOS
:%=$(PDIR
)/packages.
%.renamed
) \
272 $(REPOS
:%=$(PDIR
)/packages.
%.obsolete
)
276 .PARALLEL
: $(PKGS
) $(PROC_PKGS
) $(DEP_PKGS
) \
277 $(PROC_SYNTH_PKGS
) $(DEP_SYNTH_PKGS
) $(PUB_PKGS
)
280 # For a single manifest, the dependency chain looks like this:
282 # raw manifest (mypkg.mf)
284 # | use pkgmogrify to process raw manifest
286 # processed manifest (mypkg.mog)
288 # * | use pkgdepend generate to generate dependencies
290 # manifest with TBD dependencies (mypkg.dep)
292 # % | use pkgdepend resolve to resolve dependencies
294 # manifest with dependencies resolved (mypkg.res)
296 # | use pkgsend to publish the package
298 # placeholder to indicate successful publication (mypkg.pub)
300 # * This may be suppressed via SUPPRESSPKGDEP. The resulting
301 # packages will install correctly, but care must be taken to
302 # install all dependencies, because pkg will not have the input
303 # it needs to determine this automatically.
305 # % This is included in this diagram to make the picture complete, but
306 # this is a point of synchronization in the build process.
307 # Dependency resolution is actually done once on the entire set of
308 # manifests, not on a per-package basis.
310 # The full dependency chain for generating everything that needs to be
311 # published, without actually publishing it, looks like this:
313 # processed synthetic packages
315 # package lists synthetic package manifests
317 # processed real packages
319 # package dir real package manifests
321 # Here, each item is a set of real or synthetic packages. For this
322 # portion of the build, no reference is made to the proto area. It is
323 # therefore suitable for the "all" target, as opposed to "install."
325 # Since each of these steps is expressed explicitly, "all" need only
326 # depend on the head of the chain.
328 # From the end of manifest processing, the publication dependency
329 # chain looks like this:
331 # repository metadata (catalogs and search indices)
337 # | | pkgsend publish
339 # repositories resolved dependencies
341 # pkgsend | | pkgdepend resolve
342 # create-repository |
343 # | generated dependencies
347 # processed manifests
350 ALL_TARGETS
= $(PROC_SYNTH_PKGS
) proto_list_
$(PKGMACH
)
355 # This will build the directory to contain the processed manifests
356 # and the metadata symlinks.
359 @
print "Creating $(@)"
360 $(PKGDEBUG
)$(INS.
dir)
363 # This rule resolves dependencies across all published manifests.
365 # We shouldn't have to ignore the error from pkgdepend, but until
366 # 16012 and its dependencies are resolved, pkgdepend will always exit
369 $(PDIR
)/gendeps
: $(DEP_SYNTH_PKGS
) $(DEP_PKGS
)
370 -$(PKGDEBUG
)if
[ "$(SUPPRESSPKGDEP)" = "true" ]; then \
371 print "Suppressing dependency resolution"; \
372 for p in
$(DEP_PKGS
:%.dep
=%); do \
373 $(CP
) $$p.dep
$$p.res
; \
376 print "Resolving dependencies"; \
377 pkgdepend
-R
$(PKGDEP_RESOLVE_IMAGE
) resolve \
378 -m
$(DEP_SYNTH_PKGS
) $(DEP_PKGS
); \
379 for p in
$(DEP_SYNTH_PKGS
:%.dep
=%) $(DEP_PKGS
:%.dep
=%); do \
380 if
[ "$$(print $$p.metadata.*)" = \
381 "$$(print $$p.metadata.noincorp.*)" ]; \
383 print "Removing dependency versions from $$p"; \
384 $(PKGMOGRIFY
) $(PKGMOG_VERBOSE
) \
385 -O
$$p.res
-I transforms \
386 strip_versions
$$p.dep.res
; \
389 $(MV
) $$p.dep.res
$$p.res
; \
393 $(PKGDEBUG
)$(TOUCH
) $(@
)
395 install: $(ALL_TARGETS
) repository-metadata
397 repository-metadata
: publish_pkgs
398 $(PKGDEBUG
)for r in
$(REPOS
); do \
399 pkgrepo refresh
-s
$(PKGDEST
)/repo.
$$r; \
403 # Since we create zero-length processed manifests for a graceful abort
404 # from pkgmogrify, we need to detect that here and make no effort to
405 # publish the package.
407 # For all other packages, we publish them regardless of status. We
408 # derive the target repository as a component of the metadata-derived
409 # symlink for each package.
411 publish_pkgs
: $(REPOS
:%=$(PKGDEST
)/repo.
%) $(PDIR
)/gendeps .WAIT
$(PUB_PKGS
)
414 # Before publishing, we want to pull the license files from $CODEMGR_WS
415 # into the proto area. This allows us to NOT pass $SRC (or
416 # $CODEMGR_WS) as a basedir for publication.
418 $(PUB_PKGS
): stage-licenses
421 # Initialize the empty on-disk repositories
423 $(REPOS
:%=$(PKGDEST
)/repo.
%):
424 @
print "Initializing $(@F)"
425 $(PKGDEBUG
)$(INS.
dir)
426 $(PKGDEBUG
)pkgsend
-s file
://$(@
) create-repository \
427 --set-property publisher.
prefix=$(PKGPUBLISHER
)
430 # rule to process real manifests
432 # To allow redistributability and package status to change, we must
433 # remove not only the actual build target (the processed manifest), but
434 # also the incidental ones (the metadata-derived symlinks).
436 # If pkgmogrify exits cleanly but fails to create the specified output
437 # file, it means that it encountered an abort directive. That means
438 # that this package should not be published for this particular build
439 # environment. Since we can't prune such packages from $(PKGS)
440 # retroactively, we need to create an empty target file to keep make
441 # from trying to rebuild it every time. For these empty targets, we
442 # do not create metadata symlinks.
444 # Automatic dependency resolution to files is also done at this phase of
445 # processing. The skipped packages are skipped due to existing bugs
448 # The incorporation dependency is tricky: it needs to go into all
449 # current and renamed manifests (ie all incorporated packages), but we
450 # don't know which those are until after we run pkgmogrify. So
451 # instead of expressing it as a transform, we tack it on ex post facto.
453 # Implementation notes:
455 # - The first $(RM) must not match other manifests, or we'll run into
456 # race conditions with parallel manifest processing.
458 # - The make macros [ie $(MACRO)] are evaluated when the makefile is
459 # read in, and will result in a fixed, macro-expanded rule for each
460 # target enumerated in $(PROC_PKGS).
462 # - The shell variables (ie $$VAR) are assigned on the fly, as the rule
463 # is executed. The results may only be referenced in the shell in
464 # which they are assigned, so from the perspective of make, all code
465 # that needs these variables needs to be part of the same line of
466 # code. Hence the use of command separators and line continuation
469 # - The extract_metadata transforms are designed to spit out shell
470 # variable assignments to stdout. Those are published to the
471 # .vars temporary files, and then used as input to the eval
472 # statement. This is done in stages specifically so that pkgmogrify
473 # can signal failure if the manifest has a syntactic or other error.
474 # The eval statement should begin with the default values, and the
475 # output from pkgmogrify (if any) should be in the form of a
476 # variable assignment to override those defaults.
478 # - When this rule completes execution, it must leave an updated
479 # target file ($@) in place, or make will reprocess the package
480 # every time it encounters it as a dependency. Hence the "touch"
481 # statement to ensure that the target is created, even when
482 # pkgmogrify encounters an abort in the publish transforms.
485 .SUFFIXES
: .mf .mog .dep .res .pub
487 $(PDIR
)/%.mog
: manifests
/%.mf
488 @
print "Processing manifest $(<F)"
489 @env PKGFMT_OUTPUT
=v1 pkgfmt
-c
$<
490 $(PKGDEBUG
)$(RM
) $(@
) $(@
:%.mog
=%) $(@
:%.mog
=%.nodepend
) \
491 $(@
:%.mog
=%.lics
) $(PDIR
)/$(@F
:%.mog
=%).metadata.
* $(@
).vars
492 $(PKGDEBUG
)$(PKGMOGRIFY
) $(PKGMOG_VERBOSE
) $(PM_INC
:%= -I
%) \
493 $(PKGMOG_DEFINES
:%=-D
%) -P
$(@
).vars
-O
$(@
) \
494 $(<) $(PM_TRANSFORMS
)
495 $(PKGDEBUG
)eval REPO
=redist PKGSTAT
=current NODEPEND
=$(SUPPRESSPKGDEP
) \
496 `$(CAT) -s $(@).vars`; \
497 if
[ -f
$(@
) ]; then \
498 if
[ "$$NODEPEND" != "false" ]; then \
499 $(TOUCH
) $(@
:%.mog
=%.nodepend
); \
502 $(PDIR
)/$(@F
:%.mog
=%).metadata.
$$PKGSTAT.
$$REPO; \
503 if
[ \
( "$$PKGSTAT" = "current" \
) -o \
504 \
( "$$PKGSTAT" = "renamed" \
) ]; \
505 then
print $(PKGDEP_INCORP
) >> $(@
); \
507 print $$LICS > $(@
:%.mog
=%.lics
); \
509 $(TOUCH
) $(@
) $(@
:%.mog
=%.lics
); \
511 $(PKGDEBUG
)$(RM
) $(@
).vars
513 $(PDIR
)/%.dep
: $(PDIR
)/%.mog
514 @
print "Generating dependencies for $(<F)"
515 $(PKGDEBUG
)$(RM
) $(@
)
516 $(PKGDEBUG
)if
[ ! -f
$(@
:%.dep
=%.nodepend
) ]; then \
517 pkgdepend generate
-m
$(PKGDEP_TOKENS
:%=-D
%) $(<) \
524 # The full chain implies that there should be a .dep.res suffix rule,
525 # but dependency generation is done on a set of manifests, rather than
526 # on a per-manifest basis. Instead, see the gendeps rule above.
529 $(PDIR
)/%.pub
: $(PDIR
)/%.res
530 $(PKGDEBUG
)m
=$$(basename $(@
:%.pub
=%).metadata.
*); \
531 r
=$${m
#$(@F:%.pub=%.metadata.)+(?).}; \
532 if
[ -s
$(<) ]; then \
533 print "Publishing $(@F:%.pub=%) to $$r repository"; \
534 pkgsend
-s file
://$(PKGDEST
)/repo.
$$r publish \
535 -d
$(PKGROOT
) -d
$(TOOLSROOT
) \
536 -d license_files
-d
$(PKGROOT
)/licenses \
537 --fmri-in-manifest
--no-index
--no-catalog
$(<) \
543 # rule to build the synthetic manifests
545 # This rule necessarily has PKGDEP_TYPE that changes according to
546 # the specific synthetic manifest. Rather than escape command
547 # dependency checking for the real manifest processing, or failing to
548 # express the (indirect) dependency of synthetic manifests on real
549 # manifests, we simply split this rule out from the one above.
551 # The implementation notes from the previous rule are applicable
554 $(PROC_SYNTH_PKGS
): $(PKGLISTS
) $$(@F
:%.mog
=%.mf
)
555 @
print "Processing synthetic manifest $(@F:%.mog=%.mf)"
556 $(PKGDEBUG
)$(RM
) $(@
) $(PDIR
)/$(@F
:%.mog
=%).metadata.
* $(@
).vars
557 $(PKGDEBUG
)$(PKGMOGRIFY
) $(PKGMOG_VERBOSE
) -I transforms
-I
$(PDIR
) \
558 $(PKGMOG_DEFINES
:%=-D
%) -D PKGDEP_TYPE
=$(PKGDEP_TYPE
) \
559 -P
$(@
).vars
-O
$(@
) $(@F
:%.mog
=%.mf
) \
560 $(PM_TRANSFORMS
) synthetic
561 $(PKGDEBUG
)eval REPO
=redist PKGSTAT
=current
`$(CAT) -s $(@).vars`; \
562 if
[ -f
$(@
) ]; then \
564 $(PDIR
)/$(@F
:%.mog
=%).metadata.
$$PKGSTAT.
$$REPO; \
568 $(PKGDEBUG
)$(RM
) $(@
).vars
570 $(DEP_SYNTH_PKGS
): $$(@
:%.dep
=%.mog
)
571 @
print "Skipping dependency generation for $(@F:%.dep=%)"
572 $(PKGDEBUG
)$(CP
) $(@
:%.dep
=%.mog
) $(@
)
577 $(RM
) -r
$(CLOBBERFILES
)
580 # This rule assumes that all links in the $PKGSTAT directories
581 # point to valid manifests, and will fail the make run if one
582 # does not contain an fmri.
584 # We do this in the BEGIN action instead of using pattern matching
585 # because we expect the fmri to be at or near the first line of each input
586 # file, and this way lets us avoid reading the rest of the file after we
589 # We keep track of a failure to locate an fmri, so we can fail the
590 # make run, but we still attempt to process each package in the
591 # repo/pkgstat-specific subdir, in hopes of maybe giving some
592 # additional useful info.
594 # The protolist is used for bfu archive creation, which may be invoked
595 # interactively by the user. Both protolist and PKGLISTS targets
596 # depend on $(PROC_PKGS), but protolist builds them recursively.
597 # To avoid collisions, we insert protolist into the dependency chain
598 # here. This has two somewhat subtle benefits: it allows bfu archive
599 # creation to work correctly, even when -a was not part of NIGHTLY_OPTIONS,
600 # and it ensures that a protolist file here will always correspond to the
601 # contents of the processed manifests, which can vary depending on build
604 $(PKGLISTS
): $(PROC_PKGS
)
605 $(PKGDEBUG
)sdotr
=$(@F
:packages.
%=%); \
606 r
=$${sdotr
%.
+(?
)}; s
=$${sdotr
#+(?).}; \
607 print "Generating $$r $$s package list"; \
608 $(RM
) $(@
); $(TOUCH
) $(@
); \
614 for (i = 1; i < ARGC; i++) { \
616 e = getline f < ARGV[i]; \
617 } while ((e == 1) && (f !~ /name=pkg.fmri/)); \
620 l = split(f, a, "="); \
621 print "depend fmri=" a[l], \
622 "type=$$(PKGDEP_TYPE)"; \
624 print "no fmri in " ARGV[i] >> "/dev/stderr"; \
629 }' `find $(PDIR) -type l -a \( $(PKGS:%=-name %.metadata.$$s.$$r -o) \
630 -name NOSUCHFILE \)` >> $(@
)
633 # rules to validate proto area against manifests, check for safe
634 # file permission modes, and generate a faux proto list
636 # For the check targets, the dependencies on $(PROC_PKGS) is specified
637 # as a subordinate make process in order to suppress output.
640 @
$(MAKE
) -e
$(PROC_PKGS
) PKGMACH
=$(PKGMACH
) \
641 SUPPRESSPKGDEP
=$(SUPPRESSPKGDEP
) > /dev
/null
644 # The .lics files were created during pkgmogrification, and list the
645 # set of licenses to pull from $SRC for each package. Because
646 # licenses may be duplicated between packages, we uniquify them as
647 # well as aggregating them here.
649 license-list
: makesilent
650 $(PKGDEBUG
)( for l in
`cat $(PROC_PKGS:%.mog=%.lics)`; \
651 do
print $$l; done
) |
sort -u
> $@
654 # Staging the license and description files in the proto area allows
655 # us to do proper unreferenced file checking of both license and
656 # description files without blanket exceptions, and to pull license
657 # content without reference to $CODEMGR_WS during publication.
659 stage-licenses
: license-list FRC
660 $(PKGDEBUG
)$(MAKE
) -e
-f Makefile.lic \
661 PKGDEBUG
=$(PKGDEBUG
) LICROOT
=$(PKGROOT
)/licenses \
663 print "$(PKGROOT)/licenses/" $$0; \
664 print "$(PKGROOT)/licenses/" $$0 ".descrip"; \
665 }' license-list` > /dev
/null
;
668 @validate_pkg
-a
$(PKGMACH
) -v \
669 $(EXCEPTIONS
:%=-e
$(CODEMGR_WS
)/exception_lists
/%) \
670 -m
$(PDIR
) -p
$(PKGROOT
) -p
$(TOOLSROOT
)
673 @validate_pkg
-a
$(PKGMACH
) -M
-m
$(PDIR
) \
674 -e
$(CODEMGR_WS
)/exception_lists
/pmodes
676 check: protocmp pmodes
678 protolist
: proto_list_
$(PKGMACH
)
680 proto_list_
$(PKGMACH
): $(PROC_PKGS
)
681 @validate_pkg
-a
$(PKGMACH
) -L
-m
$(PDIR
) > $(@
)
683 $(PROC_PKGS
): $(PDIR
)
686 # This is a convenience target to allow package names to function as
687 # build targets. Generally, using it is only useful when iterating on
688 # development of a manifest.
690 # When processing a manifest, use the basename (without extension) of
691 # the package. When publishing, use the basename with a ".pub"
694 # Other than during manifest development, the preferred usage is to
695 # avoid these targets and override PKGS on the make command line and
696 # use the provided all and install targets.
698 $(PKGS
) $(SYNTH_PKGS
): $(PDIR
)/$$(@
:%=%.mog
)
700 $(PKGS
:%=%.pub
) $(SYNTH_PKGS
:%=%.pub
): $(PDIR
)/$$(@
)
703 # This is a convenience target to resolve dependencies without publishing
706 gendeps
: $(PDIR
)/gendeps
709 # These are convenience targets for cross-platform packaging. If you
710 # want to build any of "the normal" targets for a different
711 # architecture, simply use "arch/target" as your build target.
713 # Since the most common use case for this is "install," the architecture
714 # specific install targets have been further abbreviated to elide "/install."
717 $(MAKE
) -e
$(@F
) PKGMACH
=$(@D
) SUPPRESSPKGDEP
=$(SUPPRESSPKGDEP
)
719 i386 sparc
: $$(@
)/install