Difference between revisions of "Development Tricks"

From Scribus Wiki
Jump to: navigation, search
(make)
(make)
Line 5: Line 5:
  
 
== make ==
 
== make ==
There is no need to make each time, certain files like language files can just be copied.
+
 
 +
* 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"
 +
 
 
  # perhaps there can be a script here
 
  # perhaps there can be a script here
 
  # That automagically does this?
 
  # That automagically does this?

Revision as of 21:02, 20 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

make

  • 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"
# perhaps there can be a script here
# That automagically does this?

traces in the terminal

Whenever you need to understand what happens un the code, it's possible to issue some traces on the terminal using qDebug function :

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

Clean your code before issuing a patch, unless its absolutely necessary to mess the user's terminal.

Related