#
# DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
#
# under the terms of the GNU General Public License version 2 only, as
# published by the Free Software Foundation. Oracle designates this
# particular file as subject to the "Classpath" exception as provided
# by Oracle in the LICENSE file that accompanied this code.
#
# This code is distributed in the hope that it will be useful, but WITHOUT
# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
# FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
# version 2 for more details (a copy is included in the LICENSE file that
# accompanied this code).
#
# You should have received a copy of the GNU General Public License version
# 2 along with this work; if not, write to the Free Software Foundation,
# Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.
#
# Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA
# or visit www.oracle.com if you need additional information or have any
# questions.
#
#
# Makefile for building jce.jar and the various cryptographic strength
# policy jar files.
#
#
# (The terms "OpenJDK" and "JDK" below refer to OpenJDK and Sun JDK builds
# respectively.)
#
# JCE builds are very different between OpenJDK and JDK. The OpenJDK JCE
# jar files do not require signing, but those for JDK do. If an unsigned
# jar file is installed into JDK, things will break when the crypto
# routines are called.
#
# This Makefile does the "real" build of the JCE files. There are some
# javac options currently specific to JCE, so we recompile now to make
# sure any implicit compilations didn't use any incorrect flags.
#
# For OpenJDK, the jar files built here are installed directly into the
# OpenJDK.
#
# For JDK, the binaries use pre-built/pre-signed binary files stored in
# the closed workspace that are not shipped in the OpenJDK workspaces.
# We still build the JDK files here to verify the files compile, and in
# preparation for possible signing. Developers working on JCE in JDK
# must sign the JCE files before testing. The JCE signing key is kept
# separate from the JDK workspace to prevent its disclosure.
#
# be built and signed, and the resulting jar files *MUST BE CHECKED INTO
# THE CLOSED PART OF THE WORKSPACE*. This separate step *MUST NOT BE
# FORGOTTEN*, otherwise a bug fixed in the source code will not be
# reflected in the shipped binaries. The "release" target should be
# used to generate the required files.
#
#
#
# If JDK: builds but does not install.
# During full tops-down builds,
# limited policy files are copied
# If you are working in this directory
# and want to install the prebuilts,
# use the "install-prebuilt" target.
#
# If OpenJDK, does not sign
# If JDK, tries to sign
#
#
#
#
# install-jar Alias for "jar" above
#
# If OpenJDK, does not sign
# If JDK, tries to sign
# If OpenJDK, does not sign
# If JDK, tries to sign
#
# Other targets (JDK only):
#
# sign Alias for sign-jar and sign-policy
#
# release Builds all targets in preparation
# for workspace integration.
#
# install-prebuilt Installs the pre-built jar files
#
# This makefile was written to support parallel target execution.
#
BUILDDIR = ../..
#
# The following is for when we need to do postprocessing
# (signing) against a read-only build. If the OUTPUTDIR
# isn't writable, the build currently crashes out.
#
# =====================================================
# Where to place the output, in case we're building from a read-only
# build area. (e.g. a release engineering build.)
else
#
# Location for the newly built classfiles.
#
#
# Subdirectories of these are automatically included.
#
#
# Rules
#
#
# Some licensees do not get the security sources, but we still need to
# be able to build "all" for them. Check here to see if the sources were
# available. If not, then we don't need to continue this rule.
#
else
else # OPENJDK
all:
else # FILES_java/policy files available
endif # $(FILES_java)/policy files available
endif # OPENJDK
#
# We use a variety of subdirectories in the $(TEMPDIR) depending on what
# done in the unsigned area. When files are signed in JDK, they will be
# placed in the appropriate areas.
#
# =====================================================
# Build the unsigned jce.jar file. Signing comes later.
#
#
# JCE building is somewhat involved.
#
# OpenJDK: Since we do not ship prebuilt JCE files, previous compiles
# in the build may have needed JCE class signatures. There were then
# implicitly built by javac (likely using the boot javac). While using
# those class files was fine for signatures, we need to rebuild using
# the right compiler.
#
# JDK: Even through the jce.jar was previously installed, since the
# source files are accessible in the source directories, they will
# always be "newer" than the prebuilt files inside the jar, and thus
# make will always rebuild them. (We could "hide" the JCE source in a
# separate directory, but that would make the build logic for JDK and
# OpenJDK more complicated.)
#
# Thus in either situation, we shouldn't use these files.
#
# To make sure the classes were built with the right compiler options,
# delete the existing files in $(CLASSBINDIR), rebuild the right way in a
# directory under $(TEMPDIR), then copy the files back to
# $(CLASSBINDIR). Building in $(TEMPDIR) allows us to use our make
# infrastructure without modification: .classes.list, macros, etc.
#
#
# The list of directories that will be remade from scratch, using the
#
#
# Since the -C option to jar is used below, each directory entry must be
# preceded with the appropriate directory to "cd" into.
#
#
# Build jce.jar, then replace the previously built JCE files in the
# classes directory with these. This ensures we have consistently built
# files throughout the workspaces.
#
$(RM) -r $(DELETE_DIRS)
# =====================================================
# Build the unsigned policy files.
#
# these settings work for Sun's situation. This note is not
# counsel for more information.
#
#
# Build the unsigned unlimited policy files.
#
unlimited: \
#
# Build the unsigned limited policy files.
#
# NOTE: We currently do not place restrictions on our limited export
# policy. This was not a typo.
#
limited: \
# =====================================================
# Sign the various jar files. Not needed for OpenJDK.
#
else
#
# We have to remove the build dependency, otherwise, we'll try to rebuild it
# which we can't do on a read-only filesystem.
#
$(SIGNED_DIR)/jce.jar:
@if [ ! -r $(UNSIGNED_DIR)/jce.jar ] ; then \
exit 1; \
fi
# =====================================================
# Create the Release Engineering files. Signed builds,
# unlimited policy file distribution, etc.
#
$(RM) -r \
$(CP) \
$(CP) \
cd $(JCE_BUILD_DIR)/release ; \
endif # OPENJDK
# =====================================================
# Install routines.
#
#
# Install jce.jar, depending on which type is requested.
#
else
#
# Install the appropriate policy file, depending on the type of build.
#
else
$(MKDIR) -p $(POLICY_DESTDIR)
$(RM) \
$(CP) $^ $(POLICY_DESTDIR)
$(MKDIR) -p $(POLICY_DESTDIR)
$(RM) \
$(CP) $^ $(POLICY_DESTDIR)
@$(ECHO) "\n>>>Installing prebuilt JCE framework..."
$(RM) $(JAR_DESTFILE) \
$(CP) \
# =====================================================
# Support routines.
#