Bug 52431 - using kdevelop 2.x project files (.kdevprj) with gideon
Summary: using kdevelop 2.x project files (.kdevprj) with gideon
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: KDevelop Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-12-31 04:54 UTC by Mathieu Jobin
Modified: 2002-12-31 14:24 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mathieu Jobin 2002-12-31 04:54:05 UTC
Version:           3.0.0 (using KDE 3.1.0)
Installed from:    compiled sources
Compiler:          gcc version 2.95.3 20010315 (release)
OS:          Linux (i686) release 2.4.20

Hi

im using kdevelop 3.0a2

i would like to use it wilh my old project that i've created with kdevelop 2.x
but, i cant find a way to open the old project file format.

any converter ?
do you project to make kdevelop 3.0 final .kdevprj compliant ? 

thanks
Comment 1 Harald Fernengel 2002-12-31 14:24:29 UTC
import as custom project or use kdevprj2kdevelop perl script (in CVS) 
Comment 2 Mathieu Jobin 2002-12-31 18:24:51 UTC
Subject: Re:  using kdevelop 2.x project files (.kdevprj) with gideon         

: 

Quoting Harald Fernengel <harry@kdevelop.org>:

> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>      
> http://bugs.kde.org/show_bug.cgi?id=52431     
> harry@kdevelop.org changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|UNCONFIRMED                 |RESOLVED
>          Resolution|                            |FIXED
> 
> 
> 
> ------- Additional Comments From harry@kdevelop.org  2002-12-31 14:24
> -------
> import as custom project or use kdevprj2kdevelop perl script (in CVS)
> 


maybe you should add this features to kdevelop it self, the open dialog could
allow us to select .kdevprj files and the soft could proceed to the conversion...
but thanks for the advice, i will use the perl script.
thanks