Makefile revision 370
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa#
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa# CDDL HEADER START
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa#
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa# The contents of this file are subject to the terms of the
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa# Common Development and Distribution License (the "License").
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa# You may not use this file except in compliance with the License.
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa#
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa# or http://www.opensolaris.org/os/licensing.
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa# See the License for the specific language governing permissions
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa# and limitations under the License.
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa#
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa# When distributing Covered Code, include this CDDL HEADER in each
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa# file and include the License file at usr/src/OPENSOLARIS.LICENSE.
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa# If applicable, add the following below this CDDL HEADER, with the
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa# fields enclosed by brackets "[]" replaced with your own identifying
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa# information: Portions Copyright [yyyy] [name of copyright owner]
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa#
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa# CDDL HEADER END
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa#
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa# Copyright (c) 2010, 2011, Oracle and/or its affiliates. All rights reserved.
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa#
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksainclude ../make-rules/shared-macros.mk
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa# for now, the assumption is we build any directory with a Makefile. This may
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa# not always be the case. If we build a new make-like tool to drive the upper
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa# level build, it may make different decisions and will need to include
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa# appropriate dependency information.
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa# components.mk is auto-generated by the build tools. It populates the
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa# COMPONENT_DIRS macro with a list of all directories in the workspace that
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa# contain a component.
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksacomponents.mk: # Makefile # $(WS_TOP)/components
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa @echo "Generating component list..."
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa @$(BASS_O_MATIC) --workspace=$(WS_TOP) --components=paths \
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa | sed -e 's;^$(shell pwd)/;COMPONENT_DIRS += ;g' >$@
6f834e8d872b867ccae54a7a848e1db3f7857286Eugen Kuksa
-include components.mk
# depends.mk is auto-generated by concatenating 'depend.mk' files in each
# component directory.
depends.mk: components.mk
@echo "Generating component dependencies..."
@cat $(shell $(BASS_O_MATIC) --workspace=$(WS_TOP) --components=paths \
| sed -e 's;^$(shell pwd)/;;g' -e 's;$$;/depend.mk;g') >$@ \
2>/dev/null
-include depends.mk
download: TARGET = download
prep: TARGET = prep
build: TARGET = build
install: TARGET = install
publish: TARGET = publish
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
build install publish test: $(COMPONENT_DIRS)
COMPONENT_DIRS.nosetup = $(COMPONENT_DIRS:%=%.nosetup)
download prep: $(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): $(WS_LOGS) 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): $(WS_LOGS) FORCE
@cd $(@:%.nosetup=%) && echo "$(TARGET) $(@:%.nosetup=%)" && \
$(BASS_O_MATIC) $(TEMPLATE_ZONE:%=--template-zone %) \
$(@:%.nosetup=--component %) --make $(TARGET) $(LOG)
FORCE: