(This assumes that you already have a copy of the Mozilla source, and that you have also built the source so that you have a pre-existing object directory.

eclipse updating indexes heap space-1eclipse updating indexes heap space-23

This replaces the instructions below however you may still want to get familiar with them.

To generate the workspace (1) run a complete top level build, (2) run: You can expect it to take an hour or so to work through these instructions if you're doing so for the first time.

First, Eclipse needs build console output for a complete build so that it can find compiler options for as many source files as possible.

The build must be explicitly instructed to output information that allows the directory that the compiler is being invoked from to be identified (i.e., 'make' must be instructed to output "Entering directory..."/"Leaving directory..." lines).

You'll want to have at least 8 GB of RAM installed, or better yet, Eclipse provides you with the perfect excuse to upgrade to 16 GB.

:-) Download Eclipse IDE for C/C Developers from the Eclipse download page, extract the file, and put the resulting directory somewhere sensible. In case you come across it, note that you should install llvm4eclipsecdt (or if you do, don't choose its toolchain below), even if you're using clang as your compiler.This process is sometimes called "build option discovery" or "compiler option discovery".The way that Eclipse CDT does build option discovery is to scan the console output from a real build looking for lines where a compiler was invoked.Eclipse provides many features that you'll find yourself unable to live without once you start using it, but it does come with some fairly hefty system requirements.In order to work with a fully indexed Mozilla source tree, Eclipse will use 1-2 GB of RAM.FAQ: Wait, why does Eclipse need an object directory?