diff --git a/.gitignore b/.gitignore index 6787b232535..452e9f5a9d6 100644 --- a/.gitignore +++ b/.gitignore @@ -18,3 +18,6 @@ NashornProfile.txt /src/utils/LogCompilation/target/ /.project/ /.settings/ +/.project +/.classpath +/.cproject diff --git a/doc/ide.html b/doc/ide.html index d6e510319b7..18d45617f91 100644 --- a/doc/ide.html +++ b/doc/ide.html @@ -79,6 +79,45 @@ native source. After configuring, the project is generated using:
ide\hotspot-visualstudio
subfolder of the build output
folder. The file can be opened in Visual Studio via
File -> Open -> Project/Solution
.
+The make system can generate an Eclipse CDT Workspace that enables +Eclipse indexing for the C and C++ sources throughout the entire +codebase, as well as registering all common make targets to be runnable +from the Eclipse explorer. This can be done after configuring by +running:
+make eclipse-native-env
+After this is run, simply open and import the workspace in Eclipse
+through
+File -> Import -> Projects from Folder or Archive
and
+at Import source
click on the directory
+ide\eclipse
, which can be found in the build output
+folder.
If this doesn't work, you can also try
+File -> Import -> Existing Projects into Workspace
+instead.
Setting up an Eclipse Workspace is relatively lightweight compared to +other supported IDEs, but requires that your CDT installation has Cross +GCC support enabled at the moment, even if you aren't cross compiling. +The Visual C++ compiler is, at present, not supported as an indexer.
+If desired, you can instead request make to only include indexing +support for just the Java Virtual Machine instead of the entire native +codebase, by running:
+make eclipse-hotspot-env
+If you think your particular Eclipse installation can handle the +strain, the make system also supports generating a combined Java and +C/C++ Workspace for Eclipse which can then conveniently switch between +Java and C/C++ natures during development by running:
+make eclipse-mixed-env
+Do note that this generates all features that come with both Java and +C/C++ natures.
+By default, the Eclipse Workspace is located in the ide subdirectory +in the build output. To share the JDK's source directory with the +Eclipse Workspace, you can instead run:
+make eclipse-shared-<ENV>-env
+Eclipse support in the JDK is relatively new, so do keep in mind that +not everything may work at the moment. As such, the resulting Workspace +also has compilation database parsing support enabled, so you can pass +Eclipse the compile commands file (see below) if all else fails.
The make system can generate generic native code indexing support in
the form of a
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 here. Eclipse JDT is a widely used Java IDE and has been for a very long
+time, being a popular choice alongside IntelliJ IDEA for Java
+development. Likewise, the JDK now includes support for developing its
+Java sources with Eclipse, which can be achieved by setting up a Java
+Workspace by running: After the workspace has been generated you can import it in the same
+way as you would with Eclipse CDT: Follow
+ If doing so results in an error, you can also import the JDK via
+ Alternatively, if you want a Java Workspace inside the JDK's source
+directory, you can instead run: As mentioned above for Eclipse CDT, you can create a combined Java
+and C/C++ Workspace which can conveniently switch between Java and C/C++
+natures during development by running:Eclipse
+
+make eclipse-java-env
File -> Import -> Projects from Folder or Archive
and
+select the ide\eclipse
directory in the build output folder
+to import the newly created Java Workspace.File -> Import -> Existing Projects into Workspace
as
+a last resort.
+make eclipse-shared-java-env
make eclipse-mixed-env