Bug 60370 - compiler uses wrong path when looking for source files
Summary: compiler uses wrong path when looking for source files
Status: RESOLVED DUPLICATE of bug 56508
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: 2.1
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KDevelop Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-06-26 09:09 UTC by Florian Jansen
Modified: 2003-06-26 10:38 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Jansen 2003-06-26 09:09:50 UTC
Version:           2.1 (using KDE 3.0.0)
Installed from:    SuSE
Compiler:          gcc version 2.95.3 20010315 (SuSE)
OS:          Linux (i686) release 2.4.18-4GB

After compiling a source file I want to undo the errors and be positioned at the errors location in the source file by clicking on the error status line in the compiler window below. But on clicking on the error status line a message shows up saying that the specific file does not exist. This is because the compiler uses the wrong path: .../src/project_name instead of .../src/project_name/project_name as it is set automatically by KDevelopment. I cannot find a way to make the compiler use the correct path.
Comment 1 Amilcar do Carmo Lucas 2003-06-26 10:12:53 UTC
Sorry, KDevelop 2.x is no longer under development. 
 
You are strongly advised to update to the latest CVS version of KDevelop3, 
code name gideon, take a look at: 
http://www.kdevelop.org/index.html?filename=branches_compiling.html 
for all the details you need. If you find a problem or need help please send a 
mail to the mailing list: 
http://www.kdevelop.org/index.html?filename=mailinglist.html 
or drop us a line at the channel #kdevelop on the server irc.kde.org using 
ksirc, for example. 
Please use the CVS version and compile it yourself because that way you can 
easily patch it if a bug is found. 
 
KDevelop3 can import KDevelop2 projects. To do so, run the kdevprj2kdevelop 
script. 
You can have and run KDevelop3 and KDevelop2 at the same time on the same 
computer without any problems. 
So migrating is a breeze. :) 
 
P.S. : The KDevelop team closed over 390 reported bugs since the release of 
the last KDevelop2.x 
 
Comment 2 Amilcar do Carmo Lucas 2003-06-26 10:37:24 UTC
Opening, because it's a duplicate 
Comment 3 Amilcar do Carmo Lucas 2003-06-26 10:38:04 UTC

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