Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
dev:eclipse [2012/11/27 00:43]
tedfelix Update Ubuntu Issues for 12.10
dev:eclipse [2015/12/21 00:37]
tedfelix [Include Files and Symbols]
Line 1: Line 1:
 ====== Using the Eclipse IDE to work on Rosegarden ====== ====== 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:
 +
 +  * [[dev:eclipse-201510|Instructions for the autotools build system prior to November 2015]]
  
 ===== Get Rosegarden Source From SVN ===== ===== Get Rosegarden Source From SVN =====
Line 18: Line 26:
  
 ===== Get Dependencies ===== ===== 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.  This should get you very close to being able to build.+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.  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   $ sudo apt-get build-dep rosegarden
  
-===== Configure and Build ===== +If you are using jack1, this should work:
-Now it's time to try configuring the Rosegarden source.  First we need to get everything set up to run configure:+
  
-  $ make distclean+  $ sudo apt-get build-dep rosegarden
  
-It's ok if you get an error about "no makefile" on the previous step.+...and you should be ready to build.
  
-  $ sh ./bootstrap.sh+===== Build =====
  
-Now we should be able to run configure.  Here's how I run it with Ubuntu 11.10 32-bit.  I need the "--with-qtlibdir" option because Ubuntu puts the Qt libraries in an architecture-specific location:+//Note 11/21/2015: For the cmake build system prior to r14351, you must run the make-lrelease script manually at this point://
  
-  $ ./configure --enable-debug --with-qtlibdir=/usr/lib/i386-linux-gnu+  $ scripts/make-lrelease
  
-With Ubuntu 12.04 64-bit:+//See [[https://sourceforge.net/p/rosegarden/mailman/message/34620543/|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."//
  
-  $ ./configure --enable-debug --with-qtlibdir=/usr/lib/x86_64-linux-gnu+Now it's time to try building the Rosegarden source with cmake.  First, create a build directory and switch into it:
  
-There may be errors when you run configure due to missing libraries.  You'll need to track those down and re-run configure.  Once configure has run successfully to completion, you can build Rosegarden with make:+  $ 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   $ 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:
 +
 +  export QT_FATAL_WARNINGS=1
 +
 +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 ===== ===== Install Eclipse =====
 The Eclipse IDE can be downloaded here: http://www.eclipse.org/ The Eclipse IDE can be downloaded here: http://www.eclipse.org/
  
-usually 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.+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.+//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 ===== ===== Set Up Rosegarden Source Under Eclipse =====
-//Note: These instructions were developed using Eclipse 4.(Juno).//+//Note: These instructions were developed using Eclipse 4.(Mars).//
  
-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.  On the far right is a button for the "Workbench" Click it.+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.  You should now be able to build with Project > Build All (Ctrl+B).+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.
  
-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.  Set the "Project:" field by hitting the "Browse...button and selecting rosegarden-svn.  Click Apply and then 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.+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: 
 + 
 +  ${workspace_loc:/rosegarden-svn}/build 
 + 
 +Click OK 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. 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 =====+===== 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: 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:
  
Line 69: Line 113:
   /usr/include/qt4/QtXml   /usr/include/qt4/QtXml
  
-When asked if you "wish to rebuild" the index, click "Yes".  Then click "Ok" to dismiss the properties dialog.  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: For Qt5, the paths are slightly different: 
 + 
 +  /usr/include/x86_64-linux-gnu/qt5 
 +  etc... 
 + 
 +Next, click on the # Symbols tab.  Verify that "GNU C++" is still selected.  In the Symbol box, add the following symbols and values: 
 + 
 +  HAVE_ALSA     1 
 +  HAVE_LIBJACK 
 + 
 +Click Ok.  When asked if you "wish to rebuild" the index, click "Yes" 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.
  
 ===== Configuring Tabs ===== ===== Configuring Tabs =====
Line 81: Line 135:
  
 ===== Faster Builds ===== ===== 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).  This will tell make that it can run four simultaneous compiles.+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 ===== ===== 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. 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.  Set the "Save automatically before build" checkbox.  This avoids build errors if you forget to save a file that you've changed.
 +
 +===== Unlimited 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".
  
 ===== Upgrade Notes ===== ===== 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.  Key things to delete (Indigo to Juno):+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.  Key things to delete for the Indigo to Juno upgrade:
  
   rosegarden-workspace/.metadata   rosegarden-workspace/.metadata
Line 94: Line 154:
   rosegarden-workspace/rosegarden-svn/.project   rosegarden-workspace/rosegarden-svn/.project
  
-===== Ubuntu 12.04-12.10 Issues =====+Juno to Kepler had the same files and directories to delete along with a new one:
  
-==== Unity Icon ==== +  rosegarden-workspace/rosegarden-svn/.settings
-It appears that adding an icon to the dash still requires gnome-desktop-item-edit.  See the "Unity Icon" section in the "Ubuntu 11.10 Issues" below for details.+
  
-===== Ubuntu 11.10 Issues =====+===== 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.
  
-==== Black on Black Tooltips ====+==== eclipse.desktop ==== 
 +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] 
 +  Type=Application 
 +  Name=Eclipse CDT 
 +  Comment=Eclipse IDE for C/C++ 
 +  Icon=<path-to-eclipse>/icon.xpm 
 +  Exec=<path-to-eclipse>/eclipse 
 +  Terminal=false 
 +  Categories=Development 
 + 
 +You'll need to adjust the "<path-to-eclipse>" to point to where you expanded Eclipse. 
 + 
 +==== GUI ==== 
 +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: 
 +  * http://help.ubuntu.com/community/UnityLaunchersAndDesktopFiles 
 +  * http://askubuntu.com/questions/67753/how-do-i-add-an-application-to-the-dash 
 + 
 +===== 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. 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.
Line 123: Line 209:
   * http://askubuntu.com/questions/70599/how-to-change-tooltip-background-color-in-unity   * http://askubuntu.com/questions/70599/how-to-change-tooltip-background-color-in-unity
  
-==== Unity Icon ==== 
-If you want Eclipse available as a unity icon, you'll have to add a .desktop file to /usr/share/applications.  The easiest way is to use 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.  You can even drag and drop it onto the launcher if you wish. 
- 
-There are several other ways to add an application to the dash.  See this page for more: 
- 
-http://askubuntu.com/questions/67753/how-do-i-add-an-application-to-the-dash 
 
 
dev/eclipse.txt · Last modified: 2024/01/05 00:38 by tedfelix
Recent changes RSS feed Creative Commons License Valid XHTML 1.0 Valid CSS Driven by DokuWiki