[Qt-creator] Editor unable to find #include files

Pawel pawelfaron87 at wp.pl
Fri Dec 6 22:14:18 CET 2013


I was struggling with the same issue some time ago i I posted a question:

There was also thread in stackoverflow with some example how to reproduce  

Unfortunately I still have the issue, so any new advice will be very  
appreciated :)

On Fri, 06 Dec 2013 02:01:24 +0100, Steve Atkins <steve at blighty.com> wrote:

> On Dec 5, 2013, at 1:24 AM, Ziller Eike <Eike.Ziller at digia.com> wrote:
>> On Dec 4, 2013, at 11:30 PM, Steve Atkins <steve at blighty.com> wrote:
>>> I've seen a regression since 2.6.something where the code model isn't  
>>> able to find files in #include statements - they get a warning  
>>> underline, hovering over them shows "no such file or directory", and  
>>> autocompletion doesn't recognize any types defined in them. Which  
>>> include files do that is consistent, but reordering the includes  
>>> sometimes changes which are affected, apparently randomly.
>>> Possibly related, hovering over other include files shows the tool tip  
>>> "const char *" instead of the file path. I can replicate this in  
>>> 2.8.1, 3.0 beta and HEAD.
>> That could mean that some include file(s) have errors (or that Qt  
>> Creator thinks that they have.
>>> I don't see anything related in the bug tracker, and I've not yet been  
>>> able to create a reasonably sized test case that demonstrates it.
>>> Does anyone have any pointers as to where I should look to start  
>>> diagnosing what's going on?
>> Please also make sure that your .includes actually contains the  
>> directory(ies) that you need.
>> Please be aware that there was a behavior change that made Qt Creator  
>> stricter with resolving the includes, see e.g.  
>> https://bugreports.qt-project.org/browse/QTCREATORBUG-10359
> Thanks. The QTCREATOR_DUMP_FILENAME_WHILE_PARSING mentioned in that  
> ticket gave me exactly what I needed to track the problem down.
> qmake and Creator are parsing my .pro file differently, and Creator  
> failing to include another configuration file - even though there's  
> nothing relevant in the included config file - caused all the other  
> misbehaviour.
> (I'm not sure whether it's a bug in the config file or in the .pro  
> parser in Creator yet - if it turns out to be the latter I'll open a  
> bug).
> Cheers,
>   Steve
> _______________________________________________
> Qt-creator mailing list
> Qt-creator at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator

Using Opera's mail client: http://www.opera.com/mail/

More information about the Qt-creator mailing list