Mercurial > jdk8-mips64-public / changeset

     1.1 --- a/README-builds.html	Wed Mar 23 17:43:38 2011 -0700
     1.2 +++ b/README-builds.html	Mon Mar 28 00:50:19 2011 -0400
     1.3 @@ -1763,6 +1763,12 @@
     1.4                      Where each of these directories contain the import JDK image
     1.5                      for that platform.
     1.6                  </dd>
     1.7 +                <dt><a name="ALT_OPENWIN_HOME"><tt>ALT_OPENWIN_HOME</tt></a></dt>
     1.8 +                <dd>
     1.9 +		    The top-level directory of the libraries and include files for the platform's 
    1.10 +		    graphical programming environment. The default location is platform specific. 
    1.11 +		    For example, on Linux it defaults to <tt>/usr/X11R6/</tt>.
    1.12 +		</dd>
    1.13                  <dt><strong>Windows specific:</strong></dt>
    1.14                  <dd>
    1.15                      <dl>
    1.16 @@ -1791,6 +1797,81 @@
    1.17                          </dd>
    1.18                      </dl>
    1.19                  </dd>
    1.20 +                <dt><strong>Cross-Compilation Support:</strong></dt>
    1.21 +                <dd>
    1.22 +                    <dl>
    1.23 +                        <dt><a name="CROSS_COMPILE_ARCH"><tt>CROSS_COMPILE_ARCH</tt></a> </dt>
    1.24 +                        <dd>
    1.25 +                            Set to the target architecture of a cross-compilation build. If set, this
    1.26 +                            variable is used to signify that we are cross-compiling. The expectation
    1.27 +                            is that <a href="#ALT_COMPILER_PATH"><tt>ALT_COMPILER_PATH</tt></a> is set
    1.28 +                            to point to the cross-compiler and that any cross-compilation specific flags
    1.29 +                            are passed using <a href="#EXTRA_CFLAGS"><tt>EXTRA_CFLAGS</tt></a>.
    1.30 +			    The <a href="#ALT_OPENWIN_HOME"><tt>ALT_OPENWIN_HOME</tt></a> variable should 
    1.31 +			    also be set to point to the graphical header files (e.g. X11) provided with 
    1.32 +			    the cross-compiler.
    1.33 +                            When cross-compiling we skip execution of any demos etc that may be built, and
    1.34 +                            also skip binary-file verification.
    1.35 +                        </dd>
    1.36 +                        <dt><tt><a name="EXTRA_CFLAGS">EXTRA_CFLAGS</a></tt> </dt>
    1.37 +                        <dd>
    1.38 +			   Used to pass cross-compilation options to the cross-compiler.
    1.39 +                           These are added to the <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> variables. 
    1.40 +			</dd>
    1.41 +                        <dt><tt><a name="USE_ONLY_BOOTDIR_TOOLS">USE_ONLY_BOOTDIR_TOOLS</a></tt> </dt>
    1.42 +                        <dd>
    1.43 +                            Used primarily for cross-compilation builds (and always set in that case)
    1.44 +                            this variable indicates that tools from the boot JDK should be used during
    1.45 +                            the build process, not the tools (<tt>javac</tt>, <tt>javah</tt>, <tt>jar</tt>)
    1.46 +                            just built (which can't execute on the build host).
    1.47 +                        </dd>
    1.48 +                        <dt><tt><a name="HOST_CC">HOST_CC</a></tt> </dt>
    1.49 +                        <dd>
    1.50 +                            The location of the C compiler to generate programs to run on the build host.
    1.51 +                            Some parts of the build generate programs that are then compiled and executed
    1.52 +                            to produce other parts of the build. Normally the primary C compiler is used
    1.53 +                            to do this, but when cross-compiling that would be the cross-compiler and the
    1.54 +                            resulting program could not be executed. 
    1.55 +                            On Linux this defaults to <tt>/usr/bin/gcc</tt>; on other platforms it must be
    1.56 +                            set explicitly.
    1.57 +                        </dd>
    1.58 +                    </dl>
    1.59 +                <dt><strong>Specialized Build Options:</strong></dt>
    1.60 +                <dd>
    1.61 +                  Some build variables exist to support specialized build environments and/or specialized
    1.62 +                  build products. Their use is only supported in those contexts:
    1.63 +                    <dl>
    1.64 +                        <dt><tt><a name="BUILD_CLIENT_ONLY">BUILD_CLIENT_ONLY</a></tt> </dt>
    1.65 +                        <dd>
    1.66 +                            Indicates this build will only contain the Hotspot client VM. In addition to
    1.67 +                            controlling the Hotspot build target, it ensures that we don't try to copy
    1.68 +                            any server VM files/directories, and defines a default <tt>jvm.cfg</tt> file
    1.69 +                            suitable for a client-only environment. Using this in a 64-bit build will
    1.70 +                            generate a sanity warning as 64-bit client builds are not directly supported.
    1.71 +                        </dd>
    1.72 +                        <dt><tt><a name="BUILD_HEADLESS_ONLY"></a>BUILD_HEADLESS_ONLY</tt> </dt>
    1.73 +                        <dd>
    1.74 +                            Used when the build environment has no graphical capabilities at all. This
    1.75 +			    excludes building anything that requires graphical libraries to be available.
    1.76 +                        </dd>
    1.77 +                        <dt><tt><a name="JAVASE_EMBEDDED"></a>JAVASE_EMBEDDED</tt> </dt>
    1.78 +                        <dd>
    1.79 +			    Used to indicate this is a build of the Oracle Java SE Embedded product. 
    1.80 +			    This will enable the directives included in the SE-Embedded specific build 
    1.81 +			    files.
    1.82 +                        </dd>
    1.83 +                        <dt><tt><a name="LIBZIP_CAN_USE_MMAP">LIBZIP_CAN_USE_MMAP</a></tt> </dt>
    1.84 +                        <dd>
    1.85 +			    If set to false, disables the use of mmap by the zip utility. Otherwise,
    1.86 +	                    mmap will be used.
    1.87 +                        </dd>
    1.88 +                        <dt><tt><a name="COMPRESS_JARS"></a>COMPRESS_JARS</tt> </dt>
    1.89 +                        <dd>
    1.90 +			  If set to true, causes certain jar files that would otherwise be built without
    1.91 +			  compression, to use compression.
    1.92 +                        </dd>
    1.93 +                    </dl>
    1.94 +                </dd>
    1.95              </dl>
    1.96          </blockquote>
    1.97          <!-- ------------------------------------------------------ -->