KCachegrind into kdesdk?
amantia at freemail.hu
Thu Aug 28 11:05:03 BST 2003
-----BEGIN PGP SIGNED MESSAGE-----
On Thursday 28 August 2003 12:36, Josef Weidendorfer wrote:
> I need some opinions/clarifications regarding the issue in the subject.
> Last sunday I asked a few core KDE people in N7Y about importing
> KCachegrind into kdesdk. There was no objection to this, but I'm not
> really sure about the consequences of this step.
I would like to see it there.
> Benefits of course would be more i18n, better availability in KDE, and
> (hopefully) some fixes regarding style guide and other rough edges by other
> KCachegrind is a KDE application, but it is bound in now way to the
> development process of KDE applications only. The data visualized
> could be produced on any machine and with programs written in any
> language (currently it's bound to the Valgrind skin Calltree).
> Does it make sense then to put it into kdesdk?
I believe so. There are also other apps that are useful for non-KDE
> I want KCachegrind to compile on KDE 3.0, too. Is it possible to make
> separate releases able to compile on older libraries out of KDE CVS (I
> with cvs2dist). Weren't there some issues here?
You can always make a separate release. Many applications do that, including
Quanta, as we also support KDE 3.0. Personally I don't use cvs2dist, but I do
it manually. It's not so hard. ;-) The only problem can be commits by other
people which break compilation on KDE 3.0, so you must watch carefully the
commit logs and try to compile it on KDE 3.0 from time-to-time.
> Thanks for comments,
Quanta Plus developer - http://quanta.sourceforge.net
K Desktop Environment - http://www.kde.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the kde-core-devel