| Both sides previous revision
Previous revision
Next revision
|
Previous revision
Next revision
Both sides next revision
|
dev:eclipse [2020/02/05 15:49]
tedfelix [Unlimited Build Console Buffer] |
dev:eclipse [2020/09/24 23:51]
tedfelix [Set Up Rosegarden Source Under Eclipse] |
| |
| $ ./rosegarden | $ ./rosegarden |
| | |
| | ===== Development Configuration ===== |
| | |
| | Core dumps can be quite handy when debugging, but generally these are turned off to avoid wasting disk space. To turn them back on, edit ''/etc/security/limits.conf'' and add these lines: |
| | |
| | <file> |
| | * hard core unlimited |
| | * soft core unlimited |
| | </file> |
| | |
| | Reboot your machine and core dumps should be enabled. Confirm with the ''ulimit'' command: |
| | |
| | $ ulimit -c |
| | unlimited |
| |
| 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: | 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 QT_FATAL_WARNINGS=1 | 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. | 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. //[In Ubuntu 20.04 I'm getting harmless Xcb warnings in the Matrix editor that cause Rosegarden to crash. Removing QT_FATAL_WARNINGS for now. Retest at the next Ubuntu LTS release.]// |
| |
| If you just need to build Rosegarden, you can stop here. Otherwise, if you are interested in doing some development with Eclipse, read on.... | If you just need to build Rosegarden, you can stop here. Otherwise, if you are interested in doing some development with Eclipse, read on.... |
| You should now be able to build with Project > Build All (Ctrl+B). | 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. | 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. //[In Ubuntu 20.04 I'm getting harmless Xcb warnings in the Matrix editor that cause Rosegarden to crash. Removing QT_FATAL_WARNINGS for now. Retest at the next Ubuntu LTS release.]// |
| |
| 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. | 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. |
