1766                 <dt><a name="ALT_OPENWIN_HOME"><tt>ALT_OPENWIN_HOME</tt></a></dt>

  1767                 <dd>

  1768 		    The top-level directory of the libraries and include files for the platform's 

  1769 		    graphical programming environment. The default location is platform specific. 

  1770 		    For example, on Linux it defaults to <tt>/usr/X11R6/</tt>.

  1771 		</dd>

  1800                 <dt><strong>Cross-Compilation Support:</strong></dt>

  1801                 <dd>

  1802                     <dl>

  1803                         <dt><a name="CROSS_COMPILE_ARCH"><tt>CROSS_COMPILE_ARCH</tt></a> </dt>

  1804                         <dd>

  1805                             Set to the target architecture of a cross-compilation build. If set, this

  1806                             variable is used to signify that we are cross-compiling. The expectation

  1807                             is that <a href="#ALT_COMPILER_PATH"><tt>ALT_COMPILER_PATH</tt></a> is set

  1808                             to point to the cross-compiler and that any cross-compilation specific flags

  1809                             are passed using <a href="#EXTRA_CFLAGS"><tt>EXTRA_CFLAGS</tt></a>.

  1810 			    The <a href="#ALT_OPENWIN_HOME"><tt>ALT_OPENWIN_HOME</tt></a> variable should 

  1811 			    also be set to point to the graphical header files (e.g. X11) provided with 

  1812 			    the cross-compiler.

  1813                             When cross-compiling we skip execution of any demos etc that may be built, and

  1814                             also skip binary-file verification.

  1815                         </dd>

  1816                         <dt><tt><a name="EXTRA_CFLAGS">EXTRA_CFLAGS</a></tt> </dt>

  1817                         <dd>

  1818 			   Used to pass cross-compilation options to the cross-compiler.

  1819                            These are added to the <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> variables. 

  1820 			</dd>

  1821                         <dt><tt><a name="USE_ONLY_BOOTDIR_TOOLS">USE_ONLY_BOOTDIR_TOOLS</a></tt> </dt>

  1822                         <dd>

  1823                             Used primarily for cross-compilation builds (and always set in that case)

  1824                             this variable indicates that tools from the boot JDK should be used during

  1825                             the build process, not the tools (<tt>javac</tt>, <tt>javah</tt>, <tt>jar</tt>)

  1826                             just built (which can't execute on the build host).

  1827                         </dd>

  1828                         <dt><tt><a name="HOST_CC">HOST_CC</a></tt> </dt>

  1829                         <dd>

  1830                             The location of the C compiler to generate programs to run on the build host.

  1831                             Some parts of the build generate programs that are then compiled and executed

  1832                             to produce other parts of the build. Normally the primary C compiler is used

  1833                             to do this, but when cross-compiling that would be the cross-compiler and the

  1834                             resulting program could not be executed. 

  1835                             On Linux this defaults to <tt>/usr/bin/gcc</tt>; on other platforms it must be

  1836                             set explicitly.

  1837                         </dd>

  1838                     </dl>

  1839                 <dt><strong>Specialized Build Options:</strong></dt>

  1840                 <dd>

  1841                   Some build variables exist to support specialized build environments and/or specialized

  1842                   build products. Their use is only supported in those contexts:

  1843                     <dl>

  1844                         <dt><tt><a name="BUILD_CLIENT_ONLY">BUILD_CLIENT_ONLY</a></tt> </dt>

  1845                         <dd>

  1846                             Indicates this build will only contain the Hotspot client VM. In addition to

  1847                             controlling the Hotspot build target, it ensures that we don't try to copy

  1848                             any server VM files/directories, and defines a default <tt>jvm.cfg</tt> file

  1849                             suitable for a client-only environment. Using this in a 64-bit build will

  1850                             generate a sanity warning as 64-bit client builds are not directly supported.

  1851                         </dd>

  1852                         <dt><tt><a name="BUILD_HEADLESS_ONLY"></a>BUILD_HEADLESS_ONLY</tt> </dt>

  1853                         <dd>

  1854                             Used when the build environment has no graphical capabilities at all. This

  1855 			    excludes building anything that requires graphical libraries to be available.

  1856                         </dd>

  1857                         <dt><tt><a name="JAVASE_EMBEDDED"></a>JAVASE_EMBEDDED</tt> </dt>

  1858                         <dd>

  1859 			    Used to indicate this is a build of the Oracle Java SE Embedded product. 

  1860 			    This will enable the directives included in the SE-Embedded specific build 

  1861 			    files.

  1862                         </dd>

  1863                         <dt><tt><a name="LIBZIP_CAN_USE_MMAP">LIBZIP_CAN_USE_MMAP</a></tt> </dt>

  1864                         <dd>

  1865 			    If set to false, disables the use of mmap by the zip utility. Otherwise,

  1866 	                    mmap will be used.

  1867                         </dd>

  1868                         <dt><tt><a name="COMPRESS_JARS"></a>COMPRESS_JARS</tt> </dt>

  1869                         <dd>

  1870 			  If set to true, causes certain jar files that would otherwise be built without

  1871 			  compression, to use compression.

  1872                         </dd>

  1873                     </dl>

  1874                 </dd>