| Both sides previous revision
Previous revision
Next revision
|
Previous revision
Next revision
Both sides next revision
|
dev:eclipse [2018/07/01 23:29]
tedfelix [Auto-Save Before Build] |
dev:eclipse [2019/09/21 19:21]
tedfelix [Upgrade Notes] |
| |
| ===== Set Up Rosegarden Source Under Eclipse ===== | ===== Set Up Rosegarden Source Under Eclipse ===== |
| //Note: These instructions were developed using Eclipse 4.7 (Oxygen).// | //Note: These instructions were developed using Eclipse 2018-09 (4.9.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. | 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. |
| ===== Include Files and Symbols ===== | ===== 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: |
| |
| /usr/include/qt4 | |
| /usr/include/qt4/QtCore | |
| /usr/include/qt4/QtGui | |
| /usr/include/qt4/QtXml | |
| |
| Note: For Qt5, the paths are slightly different: | |
| |
| /usr/include/x86_64-linux-gnu/qt5 | /usr/include/x86_64-linux-gnu/qt5 |
| etc... | /usr/include/x86_64-linux-gnu/qt5/QtCore |
| | /usr/include/x86_64-linux-gnu/qt5/QtGui |
| | /usr/include/x86_64-linux-gnu/qt5/QtNetwork |
| | /usr/include/x86_64-linux-gnu/qt5/QtPrintSupport |
| | /usr/include/x86_64-linux-gnu/qt5/QtTest |
| | /usr/include/x86_64-linux-gnu/qt5/QtXml |
| | /usr/include/x86_64-linux-gnu/qt5/QtWidgets |
| |
| Next, click on the # Symbols tab. Verify that "GNU C++" is still selected. In the Symbol box, add the following symbols and values: | Next, click on the # Symbols tab. Verify that "GNU C++" is still selected. In the Symbol box, add the following symbols and values: |
| |
| 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. | 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:// |
| | |
| | /usr/include/qt4 |
| | /usr/include/qt4/QtCore |
| | /usr/include/qt4/QtGui |
| | /usr/include/qt4/QtXml |
| | |
| |
| ===== Configuring Tabs ===== | ===== Configuring Tabs ===== |
| |
| ===== 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 for the Indigo to Juno upgrade: | 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. |
| |
| rosegarden-workspace/.metadata | rosegarden-workspace/.metadata |
| rosegarden-workspace/rosegarden-svn/.cproject | rosegarden-workspace/rosegarden-svn/.cproject |
| rosegarden-workspace/rosegarden-svn/.project | rosegarden-workspace/rosegarden-svn/.project |
| |
| Juno to Kepler had the same files and directories to delete along with a new one: | |
| |
| rosegarden-workspace/rosegarden-svn/.settings | rosegarden-workspace/rosegarden-svn/.settings |
| |
