[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    Re: KDE/kdevplatform
From:       Evgeniy Ivanov <pfx.kde () gmail ! com>
Date:       2008-08-28 13:14:52
Message-ID: 48B6A4CC.4080900 () gmail ! com
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Andreas Pakulat wrote:
> On 27.08.08 20:25:30, Evgeniy Ivanov wrote:
>> SVN commit 853533 by eivanov:
>>
>> Debug areas correction
> 
> Please use the define thats available to set a debug area for a whole
> directory. Check out the CMakeLists.txt in all the various library and
> pugin dirs, they all have add_definition(
> -DKDE_DEFAULT_DEBUG_AREA=<number> ).
> 
>>  M  +5 -5      vcs/dvcs/ui/branchmanager.cpp  
>>  M  +1 -1      vcs/dvcs/ui/dvcsmainview.cpp  
>>  M  +1 -1      vcs/dvcs/ui/revhistory/commitView.cpp  
>>  M  +1 -1      vcs/dvcs/ui/revhistory/commitlogmodel.cpp  
>>  M  +6 -6      vcs/widgets/vcscommitdialog.cpp  
> 
> vcs library already has the debug area, so you can just remove the
> numbers in these lines completely.
>  

Sorry, didn't know about this. I added notes to
http://techbase.kde.org/Development/Tutorials/Debugging/Using_Error_Messages#Links

Andreas, you pointed me a lot of time to the things that in order should
be in techbase's common programming mistakes or in our wiki (I mean your
letters about include paths, native/UNIX paths and separators, debug
areas, rule that each method should return absolute paths, etc).
I understand it's mostly KDE specific (and some things are good for any
development), but it's better to have a list of such things.
Sure that another students, who just have begun working in KDE got some
tips too.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iEYEARECAAYFAki2pMwACgkQlUAKux/lZ6PdpgCeNYQyEv7scqWOKu6tQCiYgJwx
JaoAniCDNeDvdZ5+8FYGUioMVJzCAX8G
=6Ufc
-----END PGP SIGNATURE-----
[prev in list] [next in list] [prev in thread] [next in thread]