This is an old revision of the document!

Using the Eclipse IDE to work on Rosegarden

Older Versions

These instructions are for the cmake build system introduced November 2015.

Instructions for working with older versions of Rosegarden can be found on these pages:

Get Rosegarden Source From SVN

To get started we'll need the source code for Rosegarden. We can get a copy of it from sourceforge using subversion (svn). Since we are going to use the source with Eclipse, we'll need to make sure that we set up the directories in a way that will make Eclipse happy.

Eclipse likes to have a directory for its “workspace” and a directory within the workspace for the “project”. So I usually create a workspace directory like this:

$ mkdir rosegarden-workspace

Then I get the source into a directory within the workspace dir:

$ cd rosegarden-workspace
$ svn checkout svn+ssh:// rosegarden-svn
$ cd rosegarden-svn

Replace “userid” with your sourceforge user ID. See the subversion quick start for more ways to download.

Get Dependencies

In order to successfully build Rosegarden, there are a number of libraries you'll need. If you are using a distro with apt (Ubuntu, Debian…), you can try getting the build-dep's for Rosegarden.

For build-dep's to work, you'll need to add the appropriate source repo URIs to your sources.list. The easiest way is to use synaptic.

  1. Launch synaptic. Install it if you need to.
  2. Go to Settings > Repositories
  3. Click the Source Code checkbox. It will display a dash.
  4. Close.

Note: Ubuntu 17.10 required “xhost +si:localuser:root” before synaptic would run as root.

At this point the instructions are slightly different for jack1 vs. jack2.

If you are using jack2:

$ sudo apt-get install libjack-jackd2-dev
$ sudo apt-get build-dep rosegarden

If you are using jack1, this should work:

$ sudo apt-get build-dep rosegarden

…and you should be ready to build.


Note 11/21/2015: For the cmake build system prior to r14351, you must run the make-lrelease script manually at this point:

$ scripts/make-lrelease

See cmake and *.qm files on the dev mailing list. The message you might see if this step is forgotten: “No rule to make target '../data/./locale/ca.qm', needed by 'src/qrc_data.cxx'. Stop.”

Now it's time to try building the Rosegarden source with cmake. First, create a build directory and switch into it:

$ mkdir build
$ cd build

Then run cmake:

$ cmake .. -DCMAKE_BUILD_TYPE=Debug

There may be errors when you run cmake due to missing libraries. You'll need to track those down and re-run cmake. Once cmake has run successfully to completion, you can build Rosegarden with make:

$ make

To make sure the build was successful, try running it:

$ ./rosegarden

If you have a machine with multiple cores (who doesn't these days?) you probably want to add this to the end of your .bashrc file to tell make that it can run multiple jobs simultaneously:

export MAKEFLAGS="-j `nproc`"

This will take effect the next time you start a terminal. It should speed up the build significantly.

If you are doing a lot of development, consider adding this to your .bashrc file:


This will make sure any Qt warnings stop the run so you will notice them and fix them. This is really helpful when working with signals and slots since the compiler has no idea whether the names of signals and slots actually exist. Downside: there is a slight chance that this will cause Qt apps (built in debug mode) to crash when run from the command line.

If you just need to build Rosegarden, you can stop here. Otherwise, if you are interested in doing some development with Eclipse, read on….

Install Eclipse

The Eclipse IDE can be downloaded here:

I download the Linux C/C++ version which is usually called something like “Eclipse IDE for C/C++ Developers”. It's just a tarball you can expand and then look for the “eclipse” directory with the “eclipse” binary. That's pretty much it.

NOTE: If you upgrade your OS, it's a good idea to wipe out your Eclipse install and start fresh. There are config files within the Eclipse install directory that can get out of sync and cause trouble with a new OS.

Set Up Rosegarden Source Under Eclipse

Note: These instructions were developed using Eclipse 2019-09 (4.13.0).

Since we set up the directory structure in a way that Eclipse likes, getting Eclipse to find the source and work with it is easy. Launch Eclipse. It will first ask for the location of your workspace. Give it the rosegarden-workspace directory that we created earlier. Since this is a new workspace, you'll get the Eclipse welcome screen. In the upper right is a button for the “Workbench”. Click it.

Go to File > New > Makefile Project with Existing Code. In the “Project Name” field type rosegarden-svn. For the “Existing Code Location” provide the path to the rosegarden-svn directory. In the Toolchain list, select “Linux GCC”. Click Finish.

Next, Eclipse needs to know where the build directory is. Select the project (rosegarden-svn) in the Project Explorer on the left side then go to Project > Properties. (There's a bug in Eclipse where sometimes this menu item is disabled. Right-clicking on rosegarden-svn and picking Properties works too.) Select “C/C++ Build” on the left side. In the “Build directory:” field, add “build” to the end. The final value should be:


Click “Apply and Close” to close the project properties dialog.

You should now be able to build with Project > Build All (Ctrl+B).

To run the program, you'll need to set up a Run Configuration. Go to Run > Run Configurations. Select “C/C++ Application” and hit the New button. In the Project field, use the Browse… button to select “rosegarden-svn”. In the C/C++ Application field, use the Search Project… button to select “rosegarden”. “build/rosegarden” will appear in the field. In the Environment tab, you'll want to add QT_FATAL_WARNINGS and set it to 1 so that Rosegarden will crash on signal/slot naming errors and other issues that can only be checked at runtime.

Click Run to test. You should now be able to run with Run > Run (Ctrl+F11). You should also be able to debug with F11 or Run > Debug.

If you get an error about “The selection cannot be launched, and there are no recent launches,” you need to go back into the Run Configuration and hit the Run button in there to establish the first run. That will then be used each time F11 or Ctrl-F11 are pressed.

Include Files and Symbols

To make sure Eclipse is aware of the various Qt include files, we need to tell Eclipse where the Qt includes are located. Select the “rosegarden-svn” project in the Project Explorer and go to File > Properties. In the “type filter text” box, type “paths” and hit enter. This should get you quickly to Paths and Symbols. Click on the “Includes” tab and then the “GNU C++” language. In the “Include directories” box, add the following:


Next, click on the # Symbols tab. Verify that “GNU C++” is still selected. In the Symbol box, add the following symbols and values:


Click “Apply and Close”.

At this point you'll want to rebuild the index. (Versions prior to Neon would prompt at this point. In case yours doesn't…) Right click on rosegarden-svn in the Project Explorer and select Index > Rebuild. (This can also be accessed from the main menu: Project > C/C++ Index > Rebuild.)

It will take some time for Eclipse to rebuild the index. The “C/C++ Indexer” indicator at the bottom of the window will let you know how far along the process is.

Note: Qt4 is deprecated, but for reference, the include directories were:


Configuring Tabs

Rosegarden coding standards call for using spaces instead of tabs. To configure Eclipse, you'll need to make changes in two places.

First, the editor. Go to Window > Preferences > General > Editors > Text Editors. Here you will find an “Insert spaces for tabs” checkbox. Make sure it is checked.

Second, the code formatter. Go to Window > Preferences > C/C++ > Code Style > Formatter. Make sure the “Profile name” is “K&R [built-in]”. Click on the “Edit…” button next to the profile name. In the Indentation tab, set “Tab policy” to “Spaces only”. Change the “Profile name” to “K&R with spaces”. Click on Ok and “Apply and Close”.

Now all your tabs will be spaces.

Faster Builds

If your machine has multiple cores and/or hyperthreading, you'll want to set up make for multiple jobs (make's -j option). To do that within Eclipse, go to Window > Preferences > C/C++ > Build > Environment, add an environment variable MAKEFLAGS, and set it to “-j4” (or whatever is best for your hardware, the nproc command will tell you how many cores you've got). This will tell make that it can run four simultaneous compiles.

Scalability Mode

With large source files, many of Eclipse's features are disabled by something called “scalability mode”. Since Rosegarden has some rather large source files, this can be a problem. To adjust, go to Window > Preferences > C/C++ > Editor > Scalability. Increase the “number of lines” field from 5000 to 10000. If you end up seeing the scalability mode alert dialog, you can always increase this number even further.

Auto-Save Before Build

By default, Eclipse doesn't automatically save your files when you build. If you would prefer that behavior, go to Window > Preferences > General > Workspace > Build. Set the “Save automatically before manual build” checkbox. This avoids build errors if you forget to save a file that you've changed.

Unlimited Run Console Buffer

By default, Eclipse limits debug console output to 80,000 bytes. Rosegarden generates a lot of debug output. It's a good idea to turn this limit off. Go to Window > Preferences > Run/Debug > Console. Uncheck “Limit console output”.

Unlimited Build Console Buffer

By default, Eclipse limits build console output to 500 lines. This is not sufficient when things go wrong in template-land. Go to Window > Preferences > C/C++ > Build > Console. In the “Limit console output (number of lines)” field, enter 50000.

Search Editor Reuse

By default, Eclipse reuses the current editor window when you double-click on a search result. That means you might lose what you were looking at. To turn this off, go to Window > Preferences > General > Search. Uncheck “Reuse editors to show matches”.

Upgrade Notes

When upgrading to a new version of eclipse, it's a good idea to delete all the Eclipse config files in your workspace and project so the new version can start fresh. You'll have to go through all the configuration again, but things should be a bit more stable. Here's a list of key things to delete. Some of these might not exist depending on which version of Eclipse you are using.


Ubuntu Unity Icon

There appear to be two main ways to create an application icon in the Unity dash. The easiest is to create an eclipse.desktop file. The other way involves installing a GUI tool and using it.


Applications appear in the Unity dash based on .desktop files found in /usr/share/applications. Here's a sample /usr/share/applications/eclipse.desktop file for Eclipse:

[Desktop Entry]
Name=Eclipse CDT
Comment=Eclipse IDE for C/C++

You'll need to adjust the “<path-to-eclipse>” to point to where you expanded Eclipse.


If you prefer a GUI, you can try the GNOME desktop item editor:

sudo apt-get install gnome-panel
sudo gnome-desktop-item-edit /usr/share/applications --create-new

Give it the name “Eclipse”. Point it to the eclipse binary in the eclipse install directory. And finally, use the icon that is in the eclipse install directory. Click close, and Eclipse will now appear in the dash.

For more details, check out the following links:

High CPU Usage (Ubuntu 16.04 and Eclipse Mars)

This is a known issue with gtk3. Solution is to fall back to gtk2:

Black on Black Tooltips (Ubuntu 11.10)

When you hover over an identifier in Eclipse, you'll get a tooltip that provides some helpful information about that identifier. However, with Ubuntu 11.10's Ambiance theme, the tooltip background color is black, and Eclipse doesn't handle this correctly. It tries to display black-on-black text, which is just a little tough to read.

First, make sure you are using the Ambiance theme. Go to System Settings > Appearance and note that the theme in the lower right is “Ambiance”.

What about the other Ubuntu 11.10 themes? Radiance has the same problem. The HighContrast theme does not have this problem, but it's really ugly. And while HighContrastInverse does at least provide almost readable black on blue tooltip text, it is also pretty ugly. So, to avoid hacking anything, you could try HighContrast. But I'm betting you won't like it.

The solution I use is to hack the Ambiance theme to change the tooltip foreground color to black and the background color to white. To do this, you'll need to edit the following three files:


Search within those files for “tooltip” and you should find “tooltip_bg_color” and “tooltip_fg_color”. The syntax of each of these files is a little different, but should be pretty clear. Just change tooltip_bg_color to #ffffff and tooltip_fg_color to #000000.

You might need to log out and back in, but once these changes are picked up, tooltips in Eclipse will work fine.


dev/eclipse.1580917765.txt.gz · Last modified: 2020/02/05 16:49 by tedfelix
Recent changes RSS feed Creative Commons License Valid XHTML 1.0 Valid CSS Driven by DokuWiki