5108N/A# Copyright (c) 2007, 2012, Oracle and/or its affiliates. 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 2362N/A# published by the Free Software Foundation. Oracle designates this 0N/A# particular file as subject to the "Classpath" exception as provided 2362N/A# by Oracle 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. 2362N/A# Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA 0N/A# This file should not contain rules. 0N/A# WARNING: This file is shared with other workspaces. 0N/A# So when it includes other files, it must use JDK_TOPDIR. 0N/A# Memory related -J flags that all uses of java tools should use. 0N/A # Special flags for javac on ia64 to work around a VM problem with 0N/A # bad code generation during inlining (what version had this problem?): 0N/A # Suspect this may not be needed anymore. 0N/A# All java tools (javac, javah, and javadoc) run faster with certain java 0N/A# options, this macro should be used with all these tools. 0N/A# In particular, the client VM makes these tools run faster when 1007N/A# Options for hotspot to turn off printing of options with fastdebug version 4632N/A# MMM: is headless option necessary? 0N/A# The VM flags for javac 0N/A# 64-bit builds require a larger thread stack size. 0N/A# The jar -J options are special, must be added at the end of the command line 0N/A# JAVA_TOOLS_DIR is the default location to find Java tools to run, if 0N/A# langtools is not available. 0N/A# This should be the latest promoted JDK javac. 0N/A# Invoking the Java compiler. In leaf makefiles, choose as follows: 0N/A# -- Use JAVAC if you want to take full control of what options get 0N/A# -- Use JAVAC_CMD if you want to take the defaults given to you. 3649N/A# Some licensees do not get the Security Source bundles. We will 3649N/A# attempt at building. If sources exist, we always want to 1436N/A# Add the class version we want 2101N/A# Needed for javadoc to ensure it builds documentation 2101N/A# against the newly built classes 925N/A# Needed for JAVADOC and BOOT_JAVACFLAGS 0N/A # If no explicit tools, use boot tools (add VM flags in this case) 0N/A# Override of what javac to use (see deploy workspace) 0N/A# The bootstrap java compiler (defined as the javac in the ALT_BOOTDIR jdk). 0N/A# Will be used to compile java code used to build the jdk, e.g. class files 0N/A# created by this compiler will NOT become part of this built jdk, but just 0N/A# used to build this jdk, e.g. run with the java in the ALT_BOOTDIR jdk. 0N/A# The javac supplied with the LANGTOOLS_DIST should be used to build the 0N/A# classes that will be put into the built jdk. But note that this javac 0N/A# will use the ALT_BOOTDIR java runtime. Any classes created by the 0N/A# LANGTOOLS_DIST javac should not be run during this jdk build and indeed 0N/A# may not even run with the ALT_BOOTDIR jdk because they may be a newer 0N/A# class file version that the ALT_BOOTDIR jdk doesn't understand. 0N/A# The important observation here is that the built jdk is NOT run during 0N/A# the build. If the built jdk needs to be verified that it can build this 0N/A# same jdk, then it should be supplied to the build process as the ALT_BOOTDIR 0N/A# jdk, and this resulting built jdk should be compared to the first one. 0N/A# (They should be the same). Re-using this built jdk as the ALT_BOOTDIR 0N/A# jdk will be the only way and the recommeneded way to verify the built jdk 0N/A# can bootstrap itself. 0N/A# The javac options supplied to the boot javac is limited. This compiler 0N/A# should only be used to build the 'make/tools' sources, which are not 0N/A# class files that end up in the classes directory. 0N/A# Various tools we need to run (FIXUP: Are these the right ones?)