tag | dddb4014f9138caa17c2c706777a51b5ce1fe8cf | |
---|---|---|
tagger | teamcity <teamcity@ip-10-128-210-208.eu-west-1.compute.internal> | Sat Aug 13 02:39:50 2022 +0000 |
object | 8c02c35b024c6d8485658e194a77b9b5f07c2031 |
automatically created by TeamCity VCS labeling build feature
commit | 8c02c35b024c6d8485658e194a77b9b5f07c2031 | [log] [tgz] |
---|---|---|
author | Alexey Ushakov <alexey.ushakov@jetbrains.com> | Thu Jul 14 19:35:52 2022 +0200 |
committer | Vitaly Provodin <vitaly.provodin@jetbrains.com> | Fri Aug 12 18:48:43 2022 +0700 |
tree | bea614601876d7f7f389ee830f1720c8edec687a | |
parent | cbafe41848c50adea891fb15f17509add8e302c3 [diff] |
JBR-4573 Start/stop displaysync affects performance in metal rendering pipeline Reverted extra change
JetBrains Runtime is a fork of OpenJDK available for Windows, Mac OS X, and Linux. It includes a number enhancements in font rendering, HiDPI support, ligatures, performance improvements, and bugfixes.
Download the latest releases of JetBrains Runtime to use with JetBrains IDEs. The full list can be found on the releases page.
IDE Version | Latest JBR | Date Released |
---|---|---|
2022.2 | 17.0.3-b463.3 | 24-May-2022 |
git config --global core.autocrlf input git clone git@github.com:JetBrains/JetBrainsRuntime.git
git config --global core.autocrlf false git clone git@github.com:JetBrains/JetBrainsRuntime.git
Here are quick per-platform instructions for those who can't wait to get started. Please refer to OpenJDK build docs for in-depth coverage of all the details.
TIP: To get a preliminary report of what's missing, run
./configure
and check its output. It would usually have a meaningful advice on how to solve the problem.
Create a container:
$ cd jb/project/docker $ docker build . ... Successfully built 942ea9900054
Run these commands in the new container:
$ docker run -v `pwd`../../../../:/JetBrainsRuntime -it 942ea9900054 # cd /JetBrainsRuntime # git checkout master17 # sh ./configure # make images CONF=linux-x86_64-normal-server-release
Install the necessary tools, libraries, and headers with:
$ sudo apt-get install autoconf make build-essential libx11-dev libxext-dev libxrender-dev libxtst-dev \ libxt-dev libxrandr-dev libcups2-dev libfontconfig1-dev libasound2-dev \ java-16-amazon-corretto-jdk
Then run the following:
$ cd JetBrainsRuntime $ git checkout master17 $ sh ./configure $ make images
This will build the release configuration under ./build/linux-x86_64-server-release/
.
autoconf
, binutils
, cpio
, diffutils
, file
, gawk
, gcc-core
, make
, m4
, unzip
, zip
.From the command line:
"C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Auxiliary\Build\vcvarsall.bat" amd64 "c:\Program_Files\cygwin64\bin\mintty.exe" /bin/bash -l
The first command sets up environment variables, the second starts a Cygwin shell with the proper environment.
In the Cygwin shell:
$ cd JetBrainsRuntime $ git checkout master17 $ bash configure --with-toolchain-version=2019 $ make images
This will build the release configuration under ./build/windows-x86_64-server-release/
.
Install the following:
autoconf
via Homebrew.From the command line:
$ cd JetBrainsRuntime $ git checkout master17 $ sh ./configure $ make images
This will build the release configuration under ./build/macosx-x86_64-server-release/
.
You can use CLion to develop native parts of the JetBrains Runtime and IntelliJ IDEA for the parts written in Java. Both require projects to be created.
Run
$ make compile-commands
in the git root and open the resulting build/.../compile_commands.json
file as a project. Then use Tools | Compilation Database | Change Project Root
to point to git root of this repository.
See also this detailed step-by-step tutorial for all platforms: How to develop OpenJDK with CLion.
Run
$ sh ./bin/idea.sh
in the git root to generate project files (add --help
for options). If you have multiple configurations (for example, release
and fastdebug
), supply the --conf <conf_name>
argument. Then open the git root directory as a project in IDEA.
We are happy to receive your pull requests! Before you submit one, please sign our Contributor License Agreement (CLA).