|
5 | 5 | <meta name="generator" content="pandoc" /> |
6 | 6 | <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" /> |
7 | 7 | <title>IDE support in the JDK</title> |
8 | | - <style type="text/css"> |
9 | | - code{white-space: pre-wrap;} |
10 | | - span.smallcaps{font-variant: small-caps;} |
11 | | - span.underline{text-decoration: underline;} |
12 | | - div.column{display: inline-block; vertical-align: top; width: 50%;} |
| 8 | + <style> |
| 9 | + code{white-space: pre-wrap;} |
| 10 | + span.smallcaps{font-variant: small-caps;} |
| 11 | + div.columns{display: flex; gap: min(4vw, 1.5em);} |
| 12 | + div.column{flex: auto; overflow-x: auto;} |
| 13 | + div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;} |
| 14 | + ul.task-list{list-style: none;} |
| 15 | + ul.task-list li input[type="checkbox"] { |
| 16 | + width: 0.8em; |
| 17 | + margin: 0 0.8em 0.2em -1.6em; |
| 18 | + vertical-align: middle; |
| 19 | + } |
| 20 | + .display.math{display: block; text-align: center; margin: 0.5rem auto;} |
13 | 21 | </style> |
14 | 22 | <link rel="stylesheet" href="../make/data/docs-resources/resources/jdk-default.css" /> |
15 | 23 | <!--[if lt IE 9]> |
|
20 | 28 | <header id="title-block-header"> |
21 | 29 | <h1 class="title">IDE support in the JDK</h1> |
22 | 30 | </header> |
23 | | -<nav id="TOC"> |
| 31 | +<nav id="TOC" role="doc-toc"> |
24 | 32 | <ul> |
25 | | -<li><a href="#introduction">Introduction</a><ul> |
26 | | -<li><a href="#ide-support-for-native-code">IDE support for native code</a></li> |
27 | | -<li><a href="#ide-support-for-java-code">IDE support for Java code</a></li> |
| 33 | +<li><a href="#introduction" id="toc-introduction">Introduction</a> |
| 34 | +<ul> |
| 35 | +<li><a href="#ide-support-for-native-code" |
| 36 | +id="toc-ide-support-for-native-code">IDE support for native |
| 37 | +code</a></li> |
| 38 | +<li><a href="#ide-support-for-java-code" |
| 39 | +id="toc-ide-support-for-java-code">IDE support for Java code</a></li> |
28 | 40 | </ul></li> |
29 | 41 | </ul> |
30 | 42 | </nav> |
31 | 43 | <h2 id="introduction">Introduction</h2> |
32 | | -<p>When you are familiar with building and testing the JDK, you may want to configure an IDE to work with the source code. The instructions differ a bit depending on whether you are interested in working with the native (C/C++) or the Java code.</p> |
| 44 | +<p>When you are familiar with building and testing the JDK, you may want |
| 45 | +to configure an IDE to work with the source code. The instructions |
| 46 | +differ a bit depending on whether you are interested in working with the |
| 47 | +native (C/C++) or the Java code.</p> |
33 | 48 | <h3 id="ide-support-for-native-code">IDE support for native code</h3> |
34 | | -<p>There are a few ways to generate IDE configuration for the native sources, depending on which IDE to use.</p> |
| 49 | +<p>There are a few ways to generate IDE configuration for the native |
| 50 | +sources, depending on which IDE to use.</p> |
35 | 51 | <h4 id="visual-studio-code">Visual Studio Code</h4> |
36 | | -<p>The make system can generate a <a href="https://code.visualstudio.com">Visual Studio Code</a> workspace that has C/C++ source indexing configured correctly, as well as launcher targets for tests and the Java launcher. After configuring, a workspace for the configuration can be generated using:</p> |
| 52 | +<p>The make system can generate a <a |
| 53 | +href="https://code.visualstudio.com">Visual Studio Code</a> workspace |
| 54 | +that has C/C++ source indexing configured correctly, as well as launcher |
| 55 | +targets for tests and the Java launcher. After configuring, a workspace |
| 56 | +for the configuration can be generated using:</p> |
37 | 57 | <pre class="shell"><code>make vscode-project</code></pre> |
38 | | -<p>This creates a file called <code>jdk.code-workspace</code> in the build output folder. The full location will be printed after the workspace has been generated. To use it, choose <code>File -> Open Workspace...</code> in Visual Studio Code.</p> |
| 58 | +<p>This creates a file called <code>jdk.code-workspace</code> in the |
| 59 | +build output folder. The full location will be printed after the |
| 60 | +workspace has been generated. To use it, choose |
| 61 | +<code>File -> Open Workspace...</code> in Visual Studio Code.</p> |
39 | 62 | <h5 id="alternative-indexers">Alternative indexers</h5> |
40 | | -<p>The main <code>vscode-project</code> target configures the default C++ support in Visual Studio Code. There are also other source indexers that can be installed, that may provide additional features. It's currently possible to generate configuration for two such indexers, <a href="https://clang.llvm.org/extra/clangd/">clangd</a> and <a href="https://github.com/Andersbakken/rtags">rtags</a>. These can be configured by appending the name of the indexer to the make target, such as:</p> |
| 63 | +<p>The main <code>vscode-project</code> target configures the default |
| 64 | +C++ support in Visual Studio Code. There are also other source indexers |
| 65 | +that can be installed, that may provide additional features. It's |
| 66 | +currently possible to generate configuration for two such indexers, <a |
| 67 | +href="https://clang.llvm.org/extra/clangd/">clangd</a> and <a |
| 68 | +href="https://github.com/Andersbakken/rtags">rtags</a>. These can be |
| 69 | +configured by appending the name of the indexer to the make target, such |
| 70 | +as:</p> |
41 | 71 | <pre class="shell"><code>make vscode-project-clangd</code></pre> |
42 | | -<p>Additional instructions for configuring the given indexer will be displayed after the workspace has been generated.</p> |
| 72 | +<p>Additional instructions for configuring the given indexer will be |
| 73 | +displayed after the workspace has been generated.</p> |
43 | 74 | <h4 id="visual-studio">Visual Studio</h4> |
44 | | -<p>The make system can generate a Visual Studio project for the Hotspot native source. After configuring, the project is generated using:</p> |
| 75 | +<p>The make system can generate a Visual Studio project for the Hotspot |
| 76 | +native source. After configuring, the project is generated using:</p> |
45 | 77 | <pre class="shell"><code>make hotspot-ide-project</code></pre> |
46 | | -<p>This creates a file named <code>jvm.vcxproj</code> in <code>ide\hotspot-visualstudio</code> subfolder of the build output folder. The file can be opened in Visual Studio via <code>File -> Open -> Project/Solution</code>.</p> |
| 78 | +<p>This creates a file named <code>jvm.vcxproj</code> in |
| 79 | +<code>ide\hotspot-visualstudio</code> subfolder of the build output |
| 80 | +folder. The file can be opened in Visual Studio via |
| 81 | +<code>File -> Open -> Project/Solution</code>.</p> |
47 | 82 | <h4 id="compilation-database">Compilation Database</h4> |
48 | | -<p>The make system can generate generic native code indexing support in the form of a <a href="https://clang.llvm.org/docs/JSONCompilationDatabase.html">Compilation Database</a> that can be used by many different IDEs and source code indexers.</p> |
| 83 | +<p>The make system can generate generic native code indexing support in |
| 84 | +the form of a <a |
| 85 | +href="https://clang.llvm.org/docs/JSONCompilationDatabase.html">Compilation |
| 86 | +Database</a> that can be used by many different IDEs and source code |
| 87 | +indexers.</p> |
49 | 88 | <pre class="shell"><code>make compile-commands</code></pre> |
50 | | -<p>It's also possible to generate the Compilation Database for the HotSpot source code only, which is a bit faster as it includes less information.</p> |
| 89 | +<p>It's also possible to generate the Compilation Database for the |
| 90 | +HotSpot source code only, which is a bit faster as it includes less |
| 91 | +information.</p> |
51 | 92 | <pre class="shell"><code>make compile-commands-hotspot</code></pre> |
52 | 93 | <h3 id="ide-support-for-java-code">IDE support for Java code</h3> |
53 | 94 | <h4 id="intellij-idea">IntelliJ IDEA</h4> |
54 | | -<p>The JDK project has a script that can be used for indexing the project with IntelliJ. After configuring and building the JDK, an IntelliJ workspace can be generated by running the following command in the top-level folder of the cloned repository:</p> |
| 95 | +<p>The JDK project has a script that can be used for indexing the |
| 96 | +project with IntelliJ. After configuring and building the JDK, an |
| 97 | +IntelliJ workspace can be generated by running the following command in |
| 98 | +the top-level folder of the cloned repository:</p> |
55 | 99 | <pre class="shell"><code>bash bin/idea.sh</code></pre> |
56 | | -<p>To use it, choose <code>File -> Open...</code> in IntelliJ and select the folder where you ran the above script.</p> |
57 | | -<p>Next, configure the project SDK in IntelliJ. Open <code>File -> Project Structure -> Project</code> and select <code>build/<config>/images/jdk</code> as the SDK to use.</p> |
58 | | -<p>In order to run the tests from the IDE, you can use the JTReg plugin. Instructions for building and using the plugin can be found <a href="https://github.com/openjdk/jtreg/tree/master/plugins/idea">here</a>.</p> |
| 100 | +<p>To use it, choose <code>File -> Open...</code> in IntelliJ and |
| 101 | +select the folder where you ran the above script.</p> |
| 102 | +<p>Next, configure the project SDK in IntelliJ. Open |
| 103 | +<code>File -> Project Structure -> Project</code> and select |
| 104 | +<code>build/<config>/images/jdk</code> as the SDK to use.</p> |
| 105 | +<p>In order to run the tests from the IDE, you can use the JTReg plugin. |
| 106 | +Instructions for building and using the plugin can be found <a |
| 107 | +href="https://github.com/openjdk/jtreg/tree/master/plugins/idea">here</a>.</p> |
59 | 108 | </body> |
60 | 109 | </html> |
0 commit comments