Migrating from KDev2 to KDev3

[Tarjei Knapstad]

On Thu, 2004-03-25 at 17:06, Geoffrey Huang wrote:
> Tarjei Knapstad wrote:

<snip>

> > 1. From the documentation I read that converting a project is easy as
> > pie - just open a KDevelop 2 project file and off you go. That kind of
> > worked, but the Automake manager is missing, together with all the menu
> > options for running automake, configure and so on. Also the "Project
> > options" dialog is missing all the "usual" stuff I get when creating a
> > new autoconf/automake based project. Am I missing something, or is this
> > broken?
> 
> I did this migration a while ago, and I remember running into similar problems. 
>   To be honest, I found it easier to start from scratch and build a new project 
> with KDevelop3.  I just manually added the existing files to the new project. 
> Luckily, my project wasn't too big at the time.
> 

I'm not that lucky - our project currently contains 6-700 classes, most
with their own header/implementation file... Oh well, hopefully I'll
find a good way of doing it :) (haven't had time to play around more
yet)

Cheers,
--
Tarjei


-
to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
unsubscribe »your-email-address«