< prev index next >

README.md

Print this page

 22 There are also CLI tools available for importing OpenJDK
 23 [Mercurial](https://mercurial-scm.org/) repositories into
 24 [Git](https://git-scm.com/) repositories and vice versa:
 25 
 26 - git-openjdk-import
 27 - git-verify-import
 28 - hg-openjdk-import
 29 
 30 The following server-side tools (so called "bots") for interacting with
 31 external Git source code hosting providers are available:
 32 
 33 - hgbridge - continuously convert Mercurial repositories to git
 34 - mlbridge - bridge messages between mailing lists and pull requests
 35 - notify - send email notifications when repositories are updated
 36 - pr - add OpenJDK workflow support for pull requests
 37 - submit - example pull request test runner
 38 
 39 ## Building
 40 
 41 [JDK 12](http://jdk.java.net/12/) or later and [Gradle](https://gradle.org/)
 42 5.2.1 or later is required for building. To build the project on macOS or
 43 GNU/Linux, just run the following command from the source tree root:
 44 
 45 ```bash
 46 $ sh gradlew
 47 ```
 48 
 49 To build the project on Windows, run the following command from the source tree root:
 50 
 51 ```bat
 52 > gradlew
 53 ```
 54 
 55 The extracted jlinked image will end up in the `build` directory in the source
 56 tree root.
 57 




































 58 It is also supported to cross-jlink jimages to GNU/Linux, macOS and/or Windows from
 59 any of the aforementioned operating systems. To build all applicable jimages
 60 (including the server-side tooling), run the following command from the
 61 source tree root:
 62 
 63 ```bash
 64 sh gradlew images
 65 ```
 66 
 67 ## Installing
 68 
 69 To install the Skara tools, include the `skara.gitconfig` Git configuration
 70 file in your user-level Git configuration file. On macOS or
 71 GNU/Linux:
 72 
 73 ```bash
 74 $ git config --global include.path "$PWD/skara.gitconfig"
 75 ```
 76 
 77 On Windows:

 22 There are also CLI tools available for importing OpenJDK
 23 [Mercurial](https://mercurial-scm.org/) repositories into
 24 [Git](https://git-scm.com/) repositories and vice versa:
 25 
 26 - git-openjdk-import
 27 - git-verify-import
 28 - hg-openjdk-import
 29 
 30 The following server-side tools (so called "bots") for interacting with
 31 external Git source code hosting providers are available:
 32 
 33 - hgbridge - continuously convert Mercurial repositories to git
 34 - mlbridge - bridge messages between mailing lists and pull requests
 35 - notify - send email notifications when repositories are updated
 36 - pr - add OpenJDK workflow support for pull requests
 37 - submit - example pull request test runner
 38 
 39 ## Building
 40 
 41 [JDK 12](http://jdk.java.net/12/) or later and [Gradle](https://gradle.org/)
 42 5.6.2 or later is required for building. To build the project on macOS or
 43 GNU/Linux x64, just run the following command from the source tree root:
 44 
 45 ```bash
 46 $ sh gradlew
 47 ```
 48 
 49 To build the project on Windows x64, run the following command from the source tree root:
 50 
 51 ```bat
 52 > gradlew
 53 ```
 54 
 55 The extracted jlinked image will end up in the `build` directory in the source
 56 tree root.
 57 
 58 ### Other operating systems and CPU architectures
 59 
 60 If you want to build on an operating system other than GNU/Linux, macOS or
 61 Windows _or_ if you want to build on a CPU architecture other than x64, then
 62 ensure that you have JDK 12 or later installed locally. You can then run the
 63 following command from the source tree root:
 64 
 65 ```bash
 66 $ sh gradlew
 67 ```
 68 
 69 The extracted jlinked image will end up in the `build` directory in the source
 70 tree root.
 71 
 72 ### Offline builds
 73 
 74 If you don't want the build to automatically download any dependencies, then
 75 you must ensure that you have installed the following software locally:
 76 
 77 - JDK 12 or later
 78 - Gradle 5.6.2 or later
 79 
 80 To create a build then run the command:
 81 
 82 ```bash
 83 $ gradle offline
 84 ```
 85 
 86 _Please note_ that the above command does _not_ make use of `gradlew` to avoid
 87 downloading Gradle.
 88 
 89 The extracted jlinked image will end up in the `build` directory in the source
 90 tree root.
 91 
 92 ### Cross-linking
 93 
 94 It is also supported to cross-jlink jimages to GNU/Linux, macOS and/or Windows from
 95 any of the aforementioned operating systems. To build all applicable jimages
 96 (including the server-side tooling), run the following command from the
 97 source tree root:
 98 
 99 ```bash
100 sh gradlew images
101 ```
102 
103 ## Installing
104 
105 To install the Skara tools, include the `skara.gitconfig` Git configuration
106 file in your user-level Git configuration file. On macOS or
107 GNU/Linux:
108 
109 ```bash
110 $ git config --global include.path "$PWD/skara.gitconfig"
111 ```
112 
113 On Windows:
< prev index next >