Makefile revision 210
402N/A#
402N/A# CDDL HEADER START
402N/A#
402N/A# The contents of this file are subject to the terms of the
402N/A# Common Development and Distribution License (the "License").
402N/A# You may not use this file except in compliance with the License.
402N/A#
402N/A# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
402N/A# or http://www.opensolaris.org/os/licensing.
402N/A# See the License for the specific language governing permissions
402N/A# and limitations under the License.
402N/A#
402N/A# When distributing Covered Code, include this CDDL HEADER in each
402N/A# file and include the License file at usr/src/OPENSOLARIS.LICENSE.
402N/A# If applicable, add the following below this CDDL HEADER, with the
402N/A# fields enclosed by brackets "[]" replaced with your own identifying
402N/A# information: Portions Copyright [yyyy] [name of copyright owner]
402N/A#
402N/A# CDDL HEADER END
402N/A#
402N/A# Copyright (c) 2010, 2011, Oracle and/or its affiliates. All rights reserved.
402N/A#
402N/A
402N/Ainclude ../make-rules/shared-macros.mk
402N/A
402N/A# for now, the assumption is we build any directory with a Makefile. This may
402N/A# not always be the case. If we build a new make-like tool to drive the upper
402N/A# level build, it may make different decisions and will need to include
402N/A# appropriate dependency information.
402N/A
402N/A# components.mk is auto-generated by the build tools. It populates the
402N/A# COMPONENT_DIRS macro with a list of all directories in the workspace that
402N/A# contain a component.
402N/Acomponents.mk: # Makefile # $(WS_TOP)/components
402N/A @echo "Generating component list..."
402N/A @$(BASS_O_MATIC) --workspace=$(WS_TOP) --components=paths \
402N/A | sed -e 's;^$(shell pwd)/;COMPONENT_DIRS += ;g' >$@
402N/A
-include components.mk
download: TARGET = download
prep: TARGET = prep
build: TARGET = build
install: TARGET = install
publish: TARGET = publish
install-packages: TARGET = install-packages
validate: TARGET = validate
clean: TARGET = clean
clobber: TARGET = clobber
test: TARGET = test
prep build install publish test: TEMPLATE_ZONE=$(ZONE)
prep build install publish test: LOG = >$(WS_LOGS)/$(@F).$(TARGET).log 2>&1
# turn off pkglint for the individual component builds.
publish: MAKEFLAGS += PKGLINT=/bin/true
.DEFAULT: publish
download prep build install publish install-packages validate \
test: $(COMPONENT_DIRS)
COMPONENT_DIRS.nosetup = $(COMPONENT_DIRS:%=%.nosetup)
clean: $(COMPONENT_DIRS:%=%.nosetup)
$(RM) components.mk depends.mk .profile
clobber: $(COMPONENT_DIRS:%=%.nosetup) clean
$(RM) -r $(WS_REPO) $(WS_LOGS) $(WS_LINT_CACHE)
setup: $(WS_LOGS) $(WS_REPO) tools $(WS_LINT_CACHE)
$(WS_LOGS):
$(MKDIR) $@
$(WS_REPO):
$(PKGREPO) create $(PKG_REPO)
$(PKGREPO) add-publisher -s $(PKG_REPO) $(PUBLISHER)
$(WS_LINT_CACHE): $(WS_LOGS)
ifdef CANONICAL_REPO
@echo "Generating pkglint(1) cache from $(CANONICAL_REPO)..."
@(echo "set name=fmri value=pkg:/dummy" | $(PKGLINT) \
-c $(WS_LINT_CACHE) -r $(CANONICAL_REPO) /dev/fd/0 \
>$(WS_LOGS)/naughty-canonical-repo-actions 2>&1 ; exit 0)
else
$(MKDIR) $(WS_LINT_CACHE)
endif
tools:
@cd ../tools ; echo "building tools..." ; $(GMAKE) setup
# $(WS_COMPONENTS) is the home directory for the zone user, so create a profile
# to pass a few things on to zone based builds
.profile:
echo "PATH=$(PATH)" >>$@
echo "WS_TOP=$(WS_TOP)" >>$@
echo "export PATH WS_TOP" >>$@
$(COMPONENT_DIRS): setup FORCE
@cd $@ && echo "$(TARGET) $@" && \
$(BASS_O_MATIC) $(TEMPLATE_ZONE:%=--template-zone %) \
$(@:%=--component %) --make $(TARGET) $(LOG)
publish:
$(PKGREPO) rebuild -s $(PKG_REPO)
# pkglint all of the published manifests in one batch.
ifdef CANONICAL_REPO
@echo 'pkglinting all package manifests...'
@$(ENV) PYTHONPATH=$(WS_TOOLS)/python $(PKGLINT) \
-c $(WS_LINT_CACHE) -f $(WS_TOOLS)/pkglintrc \
$(shell find . -name 'manifest-*.published')
endif
$(COMPONENT_DIRS.nosetup): FORCE
@cd $(@:%.nosetup=%) && echo "$(TARGET) $(@:%.nosetup=%)" && \
$(BASS_O_MATIC) $(TEMPLATE_ZONE:%=--template-zone %) \
$(@:%.nosetup=--component %) --make $(TARGET) $(LOG)
# depends.mk is auto-generated by the build tools, bass-o-matic.py in particular
depends.mk: components.mk
@echo "Generating component dependencies..."
@$(BASS_O_MATIC) --workspace=$(WS_TOP) --components=depend \
| sed -e 's;$(shell pwd)/;;g' >$@
# skip dependency generation until we have a new solution for it.
#-include depends.mk
FORCE: