| Both sides previous revision
Previous revision
Next revision
|
Previous revision
|
dev:eclipse [2022/05/28 02:18]
tedfelix [Faster Builds] |
dev:eclipse [2026/01/20 21:13] (current)
tedfelix [Run-Time Environment Vars] |
| /usr/include/x86_64-linux-gnu/qt5/QtXml | /usr/include/x86_64-linux-gnu/qt5/QtXml |
| /usr/include/x86_64-linux-gnu/qt5/QtWidgets | /usr/include/x86_64-linux-gnu/qt5/QtWidgets |
| | |
| | You'll likely also want to add these non-Qt5 paths: |
| | |
| | /usr/include/lilv-0 |
| | /usr/include/gtk-2.0 |
| | /usr/include/glib-2.0 |
| |
| 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: |
| |
| HAVE_ALSA 1 | HAVE_ALSA 1 |
| HAVE_LIBJACK 1 | HAVE_LIBJACK 1 |
| | HAVE_LIBSNDFILE 1 |
| | HAVE_GTK2 1 |
| |
| Click "Apply and Close". | Click "Apply and Close". |
| |
| ===== 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, the ''nproc'' command will tell you how many cores you've got). 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. | |
| | |
| You'll probably want to do the same for the command line. Add the following to ~/.bashrc: | |
| | |
| <code bash> | |
| export MAKEFLAGS="-j `nproc`" | |
| </code> | |
| | |
| ===== Core Dumps ===== | |
| | |
| Core dumps are really helpful when Rosegarden is crashing. They can be enabled by adding the following lines to ''/etc/security/limits.conf'': | |
| | |
| <code> | |
| * hard core unlimited | |
| * soft core unlimited | |
| </code> | |
| | |
| Reboot is required for this change to take effect. Now you will get core dumps on every crash. Note that if there already is a core dump, a new one will not be created, so be sure to delete them after you are done analyzing them. Core dumps will appear in the current working directory when Rosegarden was run. | |
| |
| ===== Scalability Mode ===== | ===== Scalability Mode ===== |
| |
| ===== Massive Build Console Buffer ===== | ===== Massive 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. | 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. |
| | |
| | ===== Run-Time Environment Vars ===== |
| | |
| | Adding these at run-time can be quite handy. Go to Run > Run Configurations... > rosegarden-git Default (should already be selected) > Environment. Add these: |
| | |
| | QT_MESSAGE_PATTERN %{threadid} %{message} |
| | LD_LIBRARY_PATH build/ |
| |
| ===== Search Editor Reuse ===== | ===== Search Editor Reuse ===== |
