diff -r f75a1efb1412 -r 7f6088f46813 README-builds.html
--- a/README-builds.html Wed Jul 05 17:38:31 2017 +0200
+++ b/README-builds.html Mon Mar 28 00:50:19 2011 -0400
@@ -1763,6 +1763,12 @@
Where each of these directories contain the import JDK image
for that platform.
+
ALT_OPENWIN_HOME
+
+ The top-level directory of the libraries and include files for the platform's
+ graphical programming environment. The default location is platform specific.
+ For example, on Linux it defaults to /usr/X11R6/.
+
Windows specific:
@@ -1791,6 +1797,81 @@
+ Cross-Compilation Support:
+
+
+ - CROSS_COMPILE_ARCH
+ -
+ Set to the target architecture of a cross-compilation build. If set, this
+ variable is used to signify that we are cross-compiling. The expectation
+ is that ALT_COMPILER_PATH is set
+ to point to the cross-compiler and that any cross-compilation specific flags
+ are passed using EXTRA_CFLAGS.
+ The ALT_OPENWIN_HOME variable should
+ also be set to point to the graphical header files (e.g. X11) provided with
+ the cross-compiler.
+ When cross-compiling we skip execution of any demos etc that may be built, and
+ also skip binary-file verification.
+
+ - EXTRA_CFLAGS
+ -
+ Used to pass cross-compilation options to the cross-compiler.
+ These are added to the CFLAGS and CXXFLAGS variables.
+
+ - USE_ONLY_BOOTDIR_TOOLS
+ -
+ Used primarily for cross-compilation builds (and always set in that case)
+ this variable indicates that tools from the boot JDK should be used during
+ the build process, not the tools (javac, javah, jar)
+ just built (which can't execute on the build host).
+
+ - HOST_CC
+ -
+ The location of the C compiler to generate programs to run on the build host.
+ Some parts of the build generate programs that are then compiled and executed
+ to produce other parts of the build. Normally the primary C compiler is used
+ to do this, but when cross-compiling that would be the cross-compiler and the
+ resulting program could not be executed.
+ On Linux this defaults to /usr/bin/gcc; on other platforms it must be
+ set explicitly.
+
+
+ Specialized Build Options:
+
+ Some build variables exist to support specialized build environments and/or specialized
+ build products. Their use is only supported in those contexts:
+
+ - BUILD_CLIENT_ONLY
+ -
+ Indicates this build will only contain the Hotspot client VM. In addition to
+ controlling the Hotspot build target, it ensures that we don't try to copy
+ any server VM files/directories, and defines a default jvm.cfg file
+ suitable for a client-only environment. Using this in a 64-bit build will
+ generate a sanity warning as 64-bit client builds are not directly supported.
+
+ - BUILD_HEADLESS_ONLY
+ -
+ Used when the build environment has no graphical capabilities at all. This
+ excludes building anything that requires graphical libraries to be available.
+
+ - JAVASE_EMBEDDED
+ -
+ Used to indicate this is a build of the Oracle Java SE Embedded product.
+ This will enable the directives included in the SE-Embedded specific build
+ files.
+
+ - LIBZIP_CAN_USE_MMAP
+ -
+ If set to false, disables the use of mmap by the zip utility. Otherwise,
+ mmap will be used.
+
+ - COMPRESS_JARS
+ -
+ If set to true, causes certain jar files that would otherwise be built without
+ compression, to use compression.
+
+
+