[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 139161] QMake project appears empty after changes to it
From:       Andreas Pakulat <apaku () gmx ! de>
Date:       2006-12-23 14:41:17
Message-ID: 20061223144117.8285.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=139161         




------- Additional Comments From apaku gmx de  2006-12-23 15:41 -------
On 23.12.06 15:11:00, Christian Schneider wrote:
> Am Samstag, den 23.12.2006, 13:37 +0000 schrieb Andreas Pakulat:
> > I can reproduce a part of the problem, i.e. opening the .pro file in
> > the editor and changing sth. via the QM does give me the
> > reload-subproject dialog. However choosing either reload or no-reload
> > doesn't clear the QM.
> 
> I didn't edit or even open the .pro file in KDevelop or any other editor
> at any time. However, I can't reproduce this error every time, but quite
> often.


Ok.

> Steps to reproduce (if it occurs):
>      1. Open KDevelop. The last project gets automatically loaded.
>      2. Do some coding, don't know exactely what I did before. No .pro
>         file edited or opened.
>      3. Select the project "cell_complex" under the "src" project.
>      4. Right click any header file and choose "exclude"
>
> Result: The project tree view gets cleared, the buttons to build,
> rebuild and execute the sub-project become disabled.


Hmm, sorry, doesn't happen for me here :( And I also have no idea how
that could happen, there is AFAIK no code path from "Exclude file" to
"delete any of the project listview items"...

It happens really on any file, i.e. they don't have anything "special"
in common?

> > Also it seems that the .pro file is broken (cell_complex.pro), one
> > thing that does break the qmake parser are end-of-line markers from
> > Windows or MacOS (i.e. \r\n or \r only instead of \n) and I'm not sure
> > I can fix that so easily...
> 
> I can't imagine where this should come from,


Me neither, but to my knowledge thats all the parser cannot parse
(except for broken .pro files).

> If you need it, I can also send you the whole project with all source
> files and my .kdevelop project file.


No, I don't think thats necessary, the content of the source files
doesn't matter and neither does their existence to the QM.

All that is left is: How did you run configure on kdevelop? We had 1
bugreport where the qmake parser behaved strangely when built with -O2
and I guess that was due to some compile patches being done that
distro...

Other than that, I fear you'd have to try to debug this yourself. Of
course I can lend you a hand as to where set the breakpoints and what to
look out for. If you want to try that, I suggest we set up for a
"meeting" in IRC.

Andreas


[prev in list] [next in list] [prev in thread] [next in thread]