Bug 58755

Summary:	Errors in kdevprj2kdevelop script
Product:	[Applications] kdevelop	Reporter:	Amilcar do Carmo Lucas <a.lucas>
Component:	general	Assignee:	KDevelop Developers <kdevelop-devel>
Status:	RESOLVED INTENTIONAL
Severity:	normal	CC:	amantia
Priority:	HI
Version:	3.0.0a4
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Amilcar do Carmo Lucas 2003-05-21 17:33:43 UTC

Version:            (using KDE KDE 3.1)
Compiler:          gcc 2.95.3 
OS:          Linux

Originaly posted on http://bugs.kde.org/show_bug.cgi?id=51251 from Matia Andras

5. The "file groups" works correctly only when the entries are separated by ";". As the conversion 
 app "kdevprj2kdevelop" does not change the "," to ";", everything is put into Others. 
 Furthermore, when specifying file names instead of file mask (ie. GNU group, AUTHORS, ChangeLog,...) 
 even with ";" the files are not put in the GNU group, but in the others.

Comment 1 Amilcar do Carmo Lucas 2003-05-21 17:35:05 UTC

Marked priority HI because it's a KDevelop2 regression

Comment 2 Amilcar do Carmo Lucas 2003-07-15 19:54:48 UTC

Subject: kdevelop

CVS commit by aclu: 

Convert , into ; in the file groups.
CCMAIL: 58755@bugs.kde.org


  M +1 -0      kdevprj2kdevelop   1.3


--- kdevelop/kdevprj2kdevelop  #1.2:1.3
@@ -202,4 +202,5 @@
         next if ($group eq "");
         $pattern = $lfvgrouppattern{$group};
+        $pattern =~ s/,/;/g;
         print FILE <<EOF;
    <group pattern="$pattern" name="$group" />

Comment 3 Amilcar do Carmo Lucas 2003-07-15 21:12:59 UTC

If the files are added to the project using the Automake Manager (or other 
manager) they show up in the groups. 
So if you add AUTHORS, ChangeLog, ... to the project, they show up!

Comment 4 Amilcar do Carmo Lucas 2003-08-12 09:59:12 UTC

Ops the problem is that the files should be added to the EXTRA_DIST target and 
that one doesn't get parsed by the autotools :( 
 
And there are some Missing things in the kdevprj2kdevelop script: 
1. .kdevses import (build configurations) 
2. sub-project build parameters (lib type, LDFLAGS etc.) 
3. installation properties (right click onto the file-in-project, 
Properties...) 
 
Thanks for Iztok for pointing this out

Comment 5 Amilcar do Carmo Lucas 2006-12-05 16:17:08 UTC

KDevelop 2 is very old and this script has been removed from KDevelop4