KCachegrind into kdesdk?
dfaure at klaralvdalens-datakonsult.se
Thu Aug 28 17:36:11 BST 2003
On Thursday 28 August 2003 17:24, Josef Weidendorfer wrote:
> On Thursday 28 August 2003 13:48, Ralf Nolden wrote:
> > On Donnerstag, 28. August 2003 13:30, Josef Weidendorfer wrote:
> > > On Thursday 28 August 2003 12:05, Andras Mantia wrote:
> > > > [...]
> > > > 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
> Just checked a little bit.
> Seems more difficult if you don't have a module on your own. E.g. I can't
> insert a configure.in.in with "#MIN_CONFIG(3)".
Doesn't cvs2dist take care of that?
> And where to put my version number? I used to let automake create
> kcachegrind.spec/.lsm with the version number from configure.in.in...
And of that too? (as a cmdline argument, possibly?)
> But replacing all qDebug with kdDebug will keep me busy for hours ;-)
No, no - just use kdesdk/scripts/kDebug2kdDebug.sh
it will do 95% of the work for you.
David Faure -- faure at kde.org, dfaure at klaralvdalens-datakonsult.se
Klarälvdalens Datakonsult AB, Platform-independent software solutions
More information about the kde-core-devel