On Windows, extra care must be taken to make sure the Cygwin environment is consistent. If you need to use a network share for the source code, see below for suggestions on how to keep the build artifacts on a local disk. The build process is very disk intensive, and having slow disk access will significantly increase build times. Put the source code on a local disk, not a network share. Chances are you will hit an OS limitation during the build. This is most likely to be an issue on Windows systems.ĭo not check out the source code in a path which has a very long name or is nested many levels deep. Special Considerationsįor a smooth building experience, it is recommended that you follow these rules on where and how to check out the source code.ĭo not check out the source code in a path which contains spaces. The rest of this document assumes a working knowledge of Mercurial. If you are new to Mercurial, a good place to start is the Mercurial Beginner's Guide. JDK 8, it is recommended that you get the jdk8u forest, which contains incremental updates, instead of the jdk8 forest, which was frozen at JDK 8 GA. If you want to build an older version, e.g. At the OpenJDK Mercurial server you can see a list of all available forests. In any case, make sure you are getting the correct version. To assist you in dealing with this somewhat unusual arrangement, there are multiple tools available, which are explained below. You will need to check out all of the repositories to be able to build OpenJDK. The source code is contained not in a single Mercurial repository, but in a tree ("forest") of interrelated repositories. OpenJDK uses Mercurial for source control. See for instance OpenJDK installation for some methods of installing a prebuilt OpenJDK. If you just want to use OpenJDK and not build it yourself, this document is not for you. Building it requires a certain amount of technical expertise, a fair number of dependencies on external software, and reasonably powerful hardware. If any of these steps failed, or if you want to know more about build requirements or build functionality, please continue reading this document. Follow the instructions, and try running bash configure again. If configure fails due to missing dependencies (to either the toolchain, external libraries or the boot JDK), most of the time it prints a suggestion on how to resolve the situation on your platform. They assume that you have installed Mercurial (and Cygwin if running on Windows) and cloned the top-level OpenJDK repository that you want to build. If you are eager to try out building OpenJDK, these simple steps works most of the time.
Setting Up a Forest for Pushing Changes (defpath).Hints and Suggestions for Advanced Users.Native Compiler (Toolchain) Requirements.
0 kommentar(er)
