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 [2019/09/21 19:36]
tedfelix [Auto-Save Before Build]
dev:eclipse [2020/08/02 00:25]
tedfelix [Build]
Line 74: Line 74:
  
   $ ./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:
Line 96: Line 110:
  
 ===== Set Up Rosegarden Source Under Eclipse ===== ===== Set Up Rosegarden Source Under Eclipse =====
-//Note: These instructions were developed using Eclipse 2018-09 (4.9.0).//+//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. 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.
Line 165: Line 179:
 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. 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 Console Buffer =====+===== 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". 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".
 +
 +===== 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.
  
 ===== Search Editor Reuse ===== ===== Search Editor Reuse =====
 
 
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