On Tuesday 10 Dec 2002 4:24 am, Mario Vazquez wrote: > And KDevelop works with autoconf 2.54 with that?
I can only it say that it works for me :-), and It works with whatever autoconf2.5x is in cooker (which I think is 2.54) The main problem is that any old kdevelop projects need to have their admin directory updated - otherwise they will stop compiling with autoconf2.5 installed. But this problem is going to exist whether KDevelop is installed or not - the problem is with the admin/ directory, not with KDevelop as such. (The admin directory contains lots of files which generate the build system for a KDE application - it's all the stuff that runs when you type : make -f Makefile.common ) Cheers Jason > > > From: Jason Wood <[EMAIL PROTECTED]> > > >Reply-To: [EMAIL PROTECTED] > >To: [EMAIL PROTECTED] > >Subject: [Cooker] KDevelop and Autoconf 2.5x > >Date: Tue, 10 Dec 2002 03:19:58 +0000 > > > >Hi, > > > >I have recently had to "rpm -i --nodeps autoconf 2.5x" in order to get it > >installed to play nicely with my KDevelop generated project. > > > >I need autoconf 2.5 because I updated the admin/ directory generated by > >KDevelop to be the same as that in KDE CVS (in the kde-common folder). The > >latest version drops support for autoconf 2.13 > > > >I'm not sure if this is of use to anyone else, but I'm sure I can't be the > >only person who finds the fact that I can't install Kdevelop and > >autoconf2.5 > >at the same time damn annoying :-) so here goes : > > > >1. Grab a recent copy of the admin directory from the kde-common modules > > in KDE cvs > >2. tar.gz it. > >3. copy it to /usr/shar/apps/kdevelop/templates/admin.tar.gz > > > >Newly generated kdevelop projects will now work with autoconf 2.5 (but not > >with autoconf 2.13, but it's ok to have both installed at the same time) > > > >4. To "fix" old kdevelop projects, simply remove the admin directory that > >was > >created by KDevelop and replace it with the same one you copied into the > >kdevelop/templates folder. > > > >I'm not sure if this is of help to packagers :-) I haven't tested this > >beyond > >creating a sample project and checking that it builds and runs correctly, > >and > >I think that step 4 may be a reason not to update the kdevelop package, > > but since you cannot currently install any new KDE software from source > > if you also happen to have KDevelop on your computer, I think that there > > is a case for as well :-) > > > >Cheers, > >Jason > > > >-- > >Jason Wood > >Homepage : www.uchian.pwp.blueyonder.co.uk > > _________________________________________________________________ > MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. > http://join.msn.com/?page=features/virus -- Jason Wood Homepage : www.uchian.pwp.blueyonder.co.uk
