Makefile revision 459
160N/A# Copyright 2007-2008 Sun Microsystems, Inc. All Rights Reserved. 0N/A# DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER. 0N/A# This code is free software; you can redistribute it and/or modify it 0N/A# under the terms of the GNU General Public License version 2 only, as 0N/A# published by the Free Software Foundation. Sun designates this 0N/A# particular file as subject to the "Classpath" exception as provided 0N/A# by Sun in the LICENSE file that accompanied this code. 0N/A# This code is distributed in the hope that it will be useful, but WITHOUT 0N/A# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or 0N/A# FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License 0N/A# version 2 for more details (a copy is included in the LICENSE file that 0N/A# accompanied this code). 0N/A# You should have received a copy of the GNU General Public License version 0N/A# 2 along with this work; if not, write to the Free Software Foundation, 0N/A# Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA. 0N/A# Please contact Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, 0N/A# CA 95054 USA or visit www.sun.com if you need additional information or 0N/A# have any questions. 0N/A# Makefile for building jce.jar and the various cryptographic strength 0N/A# (The terms "OpenJDK" and "JDK" below refer to OpenJDK and Sun JDK builds 0N/A# JCE builds are very different between OpenJDK and JDK. The OpenJDK JCE 0N/A# jar files do not require signing, but those for JDK do. If an unsigned 0N/A# jar file is installed into JDK, things will break when the crypto 0N/A# routines are called. 0N/A# This Makefile does the "real" build of the JCE files. There are some 0N/A# javac options currently specific to JCE, so we recompile now to make 0N/A# sure any implicit compilations didn't use any incorrect flags. 0N/A# For OpenJDK, the jar files built here are installed directly into the 0N/A# files stored in the closed workspace that are not shipped in the 0N/A# OpenJDK workspaces. We still build the JDK files here to verify the 0N/A# files compile, and in preparation for possible signing and 0N/A# obfuscation. Developers working on JCE in JDK must sign the JCE files 0N/A# before testing: obfuscation is optional during development. The JCE 0N/A# signing key is kept separate from the JDK workspace to prevent its 0N/A# disclosure. The obfuscation tool has not been licensed for general 0N/A# SPECIAL NOTE TO JCE/JDK developers: The source files must eventually 0N/A# be built, obfuscated, signed, and the resulting jar files *MUST BE 0N/A# CHECKED INTO THE CLOSED PART OF THE WORKSPACE*. This separate step 0N/A# *MUST NOT BE FORGOTTEN*, otherwise a bug fixed in the source code will 0N/A# not be reflected in the shipped binaries. The "release" target should 0N/A# be used to generate the required files. 0N/A# There are a number of targets to help both JDK/OpenJDK developers. 0N/A# If OpenJDK, installs 0N/A# If JDK, installs prebuilt 0N/A# If OpenJDK, does not sign 0N/A# If JDK, tries to sign 0N/A# install-jar Alias for "jar" above 0N/A# If OpenJDK, does not sign 0N/A# If JDK, tries to sign 0N/A# If OpenJDK, does not sign 0N/A# If JDK, tries to sign 0N/A# Other targets (JDK only): 0N/A# sign Alias for sign-jar and sign-policy 0N/A# release Builds all targets in preparation 0N/A# for workspace integration. 0N/A# install-prebuilt Installs the pre-built jar files 0N/A# This makefile was written to support parallel target execution. 160N/A# The following is for when we need to do postprocessing 160N/A# isn't writable, the build currently crashes out. 160N/A # ===================================================== 160N/A # Where to place the output, in case we're building from a read-only 160N/A # build area. (e.g. a release engineering build.) 0N/A# Location for the newly built classfiles. 0N/A# Subdirectories of these are automatically included. 0N/A# Some licensees do not get the security sources, but we still need to 0N/A# be able to build "all" for them. Check here to see if the sources were 0N/A# available. If not, then we don't need to continue this rule. 0N/Aendif # $(FILES_java)/policy files available 0N/A# We use a variety of subdirectories in the $(TEMPDIR) depending on what 0N/A# part of the build we're doing. Both OPENJDK/JDK builds are initially 0N/A# done in the unsigned area. When files are signed or obfuscated in JDK, 0N/A# they will be placed in the appropriate areas. 0N/A# ===================================================== 0N/A# JCE building is somewhat involved. 0N/A# OpenJDK: Since we do not ship prebuilt JCE files, previous compiles 0N/A# in the build may have needed JCE class signatures. There were then 0N/A# implicitly built by javac (likely using the boot javac). While using 0N/A# those class files was fine for signatures, we need to rebuild using 0N/A# the right compiler. 0N/A# JDK: Even through the jce.jar was previously installed, since the 0N/A# source files are accessible in the source directories, they will 0N/A# always be "newer" than the prebuilt files inside the jar, and thus 0N/A# make will always rebuild them. (We could "hide" the JCE source in a 0N/A# separate directory, but that would make the build logic for JDK and 0N/A# OpenJDK more complicated.) 0N/A# Thus in either situation, we shouldn't use these files. 0N/A# To make sure the classes were built with the right compiler options, 0N/A# delete the existing files in $(CLASSBINDIR), rebuild the right way in a 0N/A# directory under $(TEMPDIR), then copy the files back to 0N/A# $(CLASSBINDIR). Building in $(TEMPDIR) allows us to use our make 0N/A# The list of directories that will be remade from scratch, using the 0N/A# Since the -C option to jar is used below, each directory entry must be 0N/A# preceded with the appropriate directory to "cd" into. 0N/A# Build jce.jar, then replace the previously built JCE files in the 0N/A# classes directory with these. This ensures we have consistently built 0N/A# files throughout the workspaces. 0N/A# ===================================================== 0N/A# Build the unsigned policy files. 0N/A# these settings work for Sun's situation. This note is not 0N/A# counsel for more information. 0N/A# Build the unsigned unlimited policy files. 0N/A# Build the unsigned limited policy files. 0N/A# NOTE: We currently do not place restrictions on our limited export 0N/A# policy. This was not a typo. 0N/A# ===================================================== 0N/A# Sign the various jar files. Not needed for OpenJDK. 160N/A# We have to remove the build dependency, otherwise, we'll try to rebuild it 160N/A# which we can't do on a read-only filesystem. 0N/A# ===================================================== 160N/A# We have to remove the build dependency, otherwise, we'll try to rebuild it 160N/A# which we can't do on a read-only filesystem. 0N/A @
# due to an obfus problem. Manually copy them to the build directory 0N/A# The current obfuscator has a limitation in that it currently only 0N/A# supports up to v49 class file format. Force v49 classfiles in our 0N/A# ===================================================== 0N/A# Create the Release Engineering files. Obfuscated builds, 0N/A# unlimited policy file distribution, etc. 0N/A# ===================================================== 0N/A# Install jce.jar, depending on which type is requested. 0N/A# Install the appropriate policy file, depending on the type of build. 0N/A @
$(ECHO) "\n>>>Installing prebuilt JCE framework..." 0N/A# =====================================================