Development Tricks: Difference between revisions
Jump to navigation
Jump to search
m (Formatting) |
|||
Line 9: | Line 9: | ||
* 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" | ||
== | == Debugging == | ||
Whenever you need to understand what happens | === 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 <code>qDebug</code> function : | ||
:<code>qDebug() << blah << "some text";</code> | |||
Note: Don't forget to <u>CLEAN YOU CODE</u> before issuing a patch | |||
== Related == | == Related == | ||
* [[Low_Hanging_Fruit]] | * [[Low_Hanging_Fruit]] | ||
* [[How_Can_I_Help]] | * [[How_Can_I_Help]] |
Revision as of 21:25, 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
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"
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