Bug 59038 - KDevelop's class browsers won't show some of the classes in my project on a seemingly random basis
Summary: KDevelop's class browsers won't show some of the classes in my project on a s...
Status: RESOLVED FIXED
Alias: None
Product: kdevplatform
Classification: Developer tools
Component: classbrowser (show other bugs)
Version: git master
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: KDevelop Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-05-27 14:18 UTC by Guido Winkelmann
Modified: 2013-03-31 01:30 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 Guido Winkelmann 2003-05-27 14:18:13 UTC
Version:           3.0.0a4 (using KDE 3.1.9)
Compiler:          gcc version 3.2.3 20030415 (Debian prerelease)
OS:          Linux (i686) release 2.4.20-openmosix-1

Some of the times that I start KDevelop, several of the classes in my project won't show up in the class browser. This happens independently of whether I choose to view the classes by namespaces or not. (I'm not using any special namespaces in my project, though.)
When I then close and restart KDevelop, I sometimes get to see all the classes again. Other times, I have to repeat this quite often until all of my classes show up again.
Unfortunately, I cannot see any specific pattern in this behaviour.

I'm using a fairly recent version checked out from CVS (HEAD), the problem has been there for some months already, though.
The rest of KDE is from CVS, too.
Compiler is gcc 3.2.3, OS is Debian GNU/Linux testing branch.
Comment 1 Robert Jonsson 2003-05-28 20:30:09 UTC
I've seen this also I'm using a regular Mandrake 9.1 system. I thought it was me doing 
something, but I've tried to restart now several times, and many of the times a lot of 
the classes in the project I'm editing are missing.  
Right now I'm using CVS as of 2003-05-27, but it has been the same in several 
versions I've tried. 
Comment 2 Robert Jonsson 2003-06-19 09:49:20 UTC
It was a while since I saw this happening. Perhaps someone can confirm this to 
still be the case or can the bug be closed? 
 
Comment 3 Amilcar do Carmo Lucas 2003-06-19 12:13:24 UTC
Please test the latest CVS. Seams to be fixed there 
Comment 4 Robert Jonsson 2003-07-29 22:51:34 UTC
Ok, doesn't seem to be fixed... 
 
Currently using gideon cvs about one week old... (definately newer than 06-19) 
 
I've tried importing the MusE codebase (muse.seh.de) and there are classes missing 
when I do this with C++autoconf selected.  
I don't know if there are any missing when importing as C++generic project, but I 
haven't found any. 
If someone wishes to reproduce, it is the muse/synti/fluid* classes that I found missing. 
/Robert 
 
Comment 5 Andreas Koepfle 2003-10-06 05:09:58 UTC
The problem with the muse files is not a classview problem but rather an autoproject "feature". 
Autoproject manager only expands variables in Makefile.am correctly if they are defined in this 
same Makefile.am. In synti/Makefile.am 
 
SUBDIRS = organ s1 stklib4 stk vam $(FLUIDSYNTHDIRS) 
 
cannot be expanded correctly as $(FLUIDSYNTHDIRS) isn't defined in this Makefile.am.  
This behaviour is deterministic (documented in AutoSubprojectView::parseSUBDIRS) and 
different from the original posters bug report. So maybe this bug can be closed, and a new 
wishlist item for autoproject smarter variable expansion created. 
 
Comment 6 Roberto Raggi 2003-10-06 23:20:04 UTC
> SUBDIRS = organ s1 stklib4 stk vam $(FLUIDSYNTHDIRS)  
you can use the #kdevelop directive. Add to your Makefile.am 
 
#kdevelop: FLUIDSYNTHDIRS = synth 
 
ciao robe 
 
Comment 7 Aleix Pol 2013-03-31 01:30:35 UTC
moving to kdevplatform's classbrowser