Update for explanation of Calligra build types

[Jaroslaw Staniek]

Hi,
Someone asks me [1] and I am not sure: this note has been introduced
by Boud [2] in Jan 2013:
"However, all Calligra applications will crash on closing with this
option enabled."

Is this still the case for Calligra apps on your systems?

It's not at least for Kexi here. Well, actually if it ever crashes on
exit it's known and narrow case (queries) but it's unrelated to choice
of build type.

For details see:
http://techbase.kde.org/Development/CMake/Addons_for_KDE#Debugging_Features_in_Detail
- just note - different "optimization" applies to DebugFull and
RelWithDebInfo.

Also, I think RelWithDebInfo is not suitable for most developers as it
makes debugging harder due to inaccurate steps coming from more
aggressive optimizations.

So, I'd like to update this section. My proposal:

"Debugging options. The default debug setting is RelWithDebInfo which
is suitable only for obtaining backtraces. If you are developing or
debugging an application by setting breakpoints, watchpoints, using
step by step command of your debugger, if you rely on assertions,
debug and warning messages, you need to replace
-DCMAKE_BUILD_TYPE=RelWithDebInfo with -DCMAKE_BUILD_TYPE=DebugFull.
This will result in slower code what can be acceptable in most cases
given the machine is fast enough. DebugFull is not intended for
production releases of the software unless you know what you're
doing."

[1] http://forum.kde.org/viewtopic.php?f=221&t=120940
[2] http://community.kde.org/index.php?title=Calligra/Building&diff=29150&oldid=29149

-- 
regards / pozdrawiam, Jaroslaw Staniek
 Kexi & Calligra & KDE | http://calligra.org/kexi | http://kde.org
 Qt for Tizen | http://qt-project.org/wiki/Tizen
 Qt Certified Specialist | http://www.linkedin.com/in/jstaniek