Makefile revision 2035
#
# CDDL HEADER START
#
# The contents of this file are subject to the terms of the
# Common Development and Distribution License (the "License").
# You may not use this file except in compliance with the License.
#
# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
# See the License for the specific language governing permissions
# and limitations under the License.
#
# When distributing Covered Code, include this CDDL HEADER in each
# file and include the License file at usr/src/OPENSOLARIS.LICENSE.
# If applicable, add the following below this CDDL HEADER, with the
# fields enclosed by brackets "[]" replaced with your own identifying
# information: Portions Copyright [yyyy] [name of copyright owner]
#
# CDDL HEADER END
#
#
# Need to preserve timestamp for Grammar files. If the pickle files are older,
# Python will try to rebuild them.
# We patch auto* files, so regenerate headers and configure
# we don't want to leak $(CC_BITS) into BASECFLAGS as it causes problems with
# python-config
# to find the ncurses headers
# enable large files how they did in JDS
# libffi for _ctypes
# because python links with $(CC) ... $(LDFLAGS) ...
# build pic
# The python build is profile-guided for studio; to see the benefits of that,
# Python must be compiled with -xO5 and a different build target must be used.
# Use of xprofile requires that the same options be used during compilation and
# linking. The targets chosen are based on Solaris 11 minimum supported system
# requirements.
# Python puts its header files in a special place.
# 64 bit shared objects need to go in a 64-bit directory
# Setup pyconfig.h file to support 32 & 64 bit.
# *.txt files in the same directory, it will rebuild them anytime you try to
# build a Python module. So here we also touch the pickle files to avoid this.
#
ASLR_MODE = $(ASLR_ENABLE)
# common targets
$(INSTALL_32): $(INSTALL_64)
build: $(BUILD_32_and_64)
# Using "-uall,-network" ensures all tests are run except the network tests.
# The network tests contain many expected failures when run behind a firewall.
# The "-v" ensures verbose mode. You can set TESTOPTS_PYTHON_TEST to a
# particular test if you want to run just one test. For example, run gmake with
# "-k" so it continues and does both 32-bit and 64-bit tests, even if there is a
# failure, like this:
# $ TESTOPTS_PYTHON_TEST=test_sys gmake -k test
# Note that when a test succeeds, the builds/*/.tested file gets created. You
# may need to remove these files, or run "gmake clobber" or "gmake clean"
# between tests.
#
COMPONENT_TEST_TARGETS = test
test: $(TEST_32_and_64)