Bug 32677 - problem generating QT template project
Summary: problem generating QT template project
Status: RESOLVED DUPLICATE of bug 30097
Alias: None
Product: kdevelop
Classification: Applications
Component: kdevelop 2.x (obsolete) (show other bugs)
Version: 2.0.1
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KDevelop-Devel List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-09-19 17:33 UTC by Christoph Tapler
Modified: 2002-09-22 09:37 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 Christoph Tapler 2001-09-19 17:30:17 UTC
(*** This bug was imported into bugs.kde.org ***)

Package:           kdevelop
Version:           2.0.1 (using KDE 2.2.1 )
Severity:          normal
Installed from:    SuSE
Compiler:          gcc version 2.95.3 20010315 (SuSE)
OS:                Linux (i686) release 2.4.7
OS/Compiler notes: 

When I try to generate a Qt template project kdevelop complains about not finding a couple of files.
I have observed this behaviour and found out following:

The file processes.pl will be started to generate the template files. But this template assumes that the settings are in ~/.kde . That's for example _not_ true for me. In my case my settings can be found in ~/.kde2
And for that reason it's clear why kdevelop can't find the entries.* - files in this directory. I've tried to make a soft link from ~/.kde to ~/.kde2 and it worked.

A more technical description:
The first problem occures in line 14 of processes.pl: It geneartes a path which is not valid (respectively does have a different $KDEHOME as KDE has)

The problem arises in line 24 where kdevelop tries to open the (not existent) file

If you want further information email me. 
Hint: If you need a better description and you are able to read german - my german is better ;-)

(Submitted via bugs.kde.org)
(Called from KBugReport dialog)
Comment 1 John Firebaugh 2002-09-22 09:37:44 UTC

*** This bug has been marked as a duplicate of 30097 ***