moveing a application over to KDE2.0

[David Grill Watson]

Complicated? Naww....

I took a script which I found on Freshmeat (I think it was freshmeat) and 
hacked it up a bit - now all I have to do is cvsup and run the script... if 
one of the modules doesn't compile, it stops.  I'm going to hack it a little 
so that it will ask me if I want to continue with the compilation (some 
things, e.g. KOffice, never compile :).

If anyone wants it, just ask me.

On Fri, 24 Mar 2000, you wrote:
> My comment was not intended to, bash, KDE 2.0 or anything along those
> lines. I too compile the CVS releases of KDE 2.0 from time to time (perhaps
> once a week, definitely not daily (-: ). But what I intended to say was, it
> is a little complicated to be continually doing this. His question was so
> general it was quite clear to me, no offense intended, that he was quite
> new to the whole ordeal.
>
> All in all, KDE kicks ass (-:
>
> mike
>
> Martin Piskernig wrote:
> > On Fri, 24 Mar 2000, you wrote:
> > > One quick thing, QT 2.0 is fine, sure. good deal whatever, BUT
> > > KDE 2.0 is called the *KRASH* release, it's still in alpha I believe,
> > > DON'T run it. If your a develop that really wants to develop for kde
> > > 2.0 to keep most current, you should be able to figure this out on your
> > > own. I'd recommend using the latest stable release of KDE.
> >
> > I update the KDE2 cvs sources nearly daily and it is working quite good
> > right now, so if you know how to use cvsup I would definitly give it a
> > try. (Note: You will need to update your autoconf/automake stuff in your
> > application.) Apart from that, you will need Qt 2.1 (available as beta3),
> > NOT Qt 2.0 for KDE2. --
> > Martin Piskernig
> > <mpiskernig at kdevelop.de>       ICQ: 24015591
> > The KDevelop Team           www.kdevelop.org