Skip to content

Latest commit

 

History

History
42 lines (30 loc) · 2.16 KB

README.md

File metadata and controls

42 lines (30 loc) · 2.16 KB

Welcome to graal-jvmci-8

This is a fork of http://hg.openjdk.java.net/jdk8u/jdk8u/hotspot that includes JVMCI.

Building JVMCI JDK 8

To create a JVMCI-enabled JDK 8, make sure you have mx on your system. Then run the following commands:

git clone https://github.com/graalvm/graal-jvmci-8
cd graal-jvmci-8
mx --java-home /path/to/jdk8 build
mx --java-home /path/to/jdk8 unittest
export JAVA_HOME=$(mx --java-home /path/to/jdk8 jdkhome)

You need to use the same JDK the GitHub downloads are based on as the argument to --java-home in the above commands. The build step above should work on all supported JDK 8 build platforms. It should also work on other platforms (such as Oracle Linux, CentOS and Fedora as described here). If you run into build problems, send a message to http://mail.openjdk.java.net/mailman/listinfo/graal-dev.

The patches in patches/jdk are applied (in sort order of patch file name) to the JDK8 sources when building a JVMCI-enabled JDK 8. When building the JDK static libraries, the patches in patches/static-libs are applied in addition.

Windows Specifics

Building JDK requires some bash-like environment. Fortunately, the one that comes as a part of the standard Git for Windows installation will suffice, in which case you will have to set MKS_HOME to point to the directory with Linux tools, e.g.:

set MKS_HOME=<GIT_DIR>\usr\bin

where <GIT_DIR> is a path to your Git installation directory. It is important that there are NO spaces in the path, otherwise the build will fail.

You will also need an MSVC 2010 SP1 compiler. The following tool chain is recommended:

  1. Microsoft Windows SDK for Windows 7 and .NET Framework 4 (ISO)
  2. Microsoft Visual C++ 2010 Service Pack 1 Compiler Update for the Windows SDK 7.1