It’s too slow both for building and for Eclipse. Don‘t put your checkout on a remote file system (e.g.A short word about pathsīefore you start setting up your work space - here are a few hints:

This occurs on the UI thread and can result in the reading of jar files on the Eclipse classpath, which can tie up the editor due to the size of the classpath in Chromium. Pressing the control key on (for keyboard shortcuts such as copy/paste) can trigger the hyperlink detector. (Window -> Preferences, search for 'Hyperlinking, and uncheck “Enable on demand hyperlink style navigation”). Turn off Hyperlink detection in the Eclipse preferences.The large heap size prevents out of memory errors if you include many Chrome subprojects that Eclipse is maintaining code indices for. Googlers: Edit ~/.eclipse/init.sh to add this:.Change -Xms40m to -Xms1024m (minimum heap) and -Xmx256m to -Xmx3072m (maximum heap).Unpack the distribution and edit the eclipse/eclipse.ini to increase the heap available to java.Just uncheck all the boxes at first launch. The UI will be much more responsive if you do not install the google3 plug-ins.

Googlers: The version installed on Goobuntu works fine.

Best to get them all from the same source.

Tip: The packaged version of eclipse in distros may not work correctly with the latest CDT plugin (installed below).

For example, for Linux 64-bit/Java 64-bit, use the Linux 64 bit package (Eclipse Packages Tab -> Linux 64 bit (link in bottom right)).

Download the distribution appropriate for your OS.

Optional: static code and style guide analysis using cpplint.pyĮclipse 4.6.1 (Neon) is known to work with Chromium for Linux.

Alternative: Per-file accurate include/pre-processor information.

How to use eclipse as c parser