Difference between revisions of "Development Tricks"

From Scribus Wiki
Jump to navigation Jump to search
m
Line 8: Line 8:
 
:<code>-DWANT_GUI_LANG="en_GB;de;fr;it;en"</code> to your cmake command.
 
:<code>-DWANT_GUI_LANG="en_GB;de;fr;it;en"</code> to your cmake command.
 
* if you know that only a single object file has been written by "make" (as an example when you're modifying the source of a plugin), if you're on a slow computer you can speed up the compile/run/tweak cycle by manually copying the object file to the binary directory, instead of doing "make install"
 
* if you know that only a single object file has been written by "make" (as an example when you're modifying the source of a plugin), if you're on a slow computer you can speed up the compile/run/tweak cycle by manually copying the object file to the binary directory, instead of doing "make install"
 +
* use all the cores of your CPU to compile faster. That's the -j option. If you got 8 cores, use : make -j8
  
 
== Debugging ==
 
== Debugging ==

Revision as of 20:21, 21 January 2014


Background

This page shows a list of time-saving workflow tips for Devs who are developing for Scribus. Feel free to add your shortcuts

Time Reducing Strategies

  • reduce the number of files copied in the "make install" step by limiting the number of used languages to the minimum necessary. For this, add:
-DWANT_GUI_LANG="en_GB;de;fr;it;en" to your cmake command.
  • if you know that only a single object file has been written by "make" (as an example when you're modifying the source of a plugin), if you're on a slow computer you can speed up the compile/run/tweak cycle by manually copying the object file to the binary directory, instead of doing "make install"
  • use all the cores of your CPU to compile faster. That's the -j option. If you got 8 cores, use : make -j8

Debugging

Traces in the terminal

Whenever you need to understand what happens in the code, it's possible to output traces in to the terminal using qDebug function :

qDebug() << blah << "some text";

Note: Don't forget to CLEAN YOU CODE before issuing a patch

Qt

QtCreator_-_workflow_for_Scribus_and_Git_repository_under_Linux

Related