Bug#33567: Clicking an error pops "file does not exist"

pascal at sakura.email.ne.jp pascal at sakura.email.ne.jp
Thu Oct 11 08:03:11 UTC 2001


Package: kdevelop
Version: 2.0.1 (using KDE 2.2.1 )
Severity: normal
Installed from:    Mandrake Linux Vitamin
Compiler:          gcc version 2.96 20000731 (Mandrake Linux 8.1 2.96-0.62mdk)
OS:                Linux (i686) release 2.4.8-26mdksmp
OS/Compiler notes: 

I have configured kdevelop so that the
root of my source is /home/pascal/develop.
Two things are quite strange:

1. The first might be a feature, but it may
be worth reporting it.
When I create a new project, I get the
following: for instance, my project name
is "MyTest".
KDevelop then creates (in my case):
/home/pascal/Develop/mytest, which sounds
logical.
It also creates:
/home/pascal/Develop/mytest/mytest where
the source files are located.

2. After I compile, I usually get errors :-<
If I click for instance on an error located
in mytest.cpp, I get the message:
/home/pascal/mytest/mytest.cpp : file
does not exist. Indeed it does not since it
is located on level deeper :
/home/pascal/mytest/mytest/mytest.cpp

So there is an inconsistency between the
code generation and the compilation / error
processing. Beside that, the compiler
finds the file, and when there are no
compilation errors, the output works fine,
at least as I thought it would.



(Submitted via bugs.kde.org)
(Called from KBugReport dialog)


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



More information about the KDevelop-devel mailing list