[Qt-creator] Qt Creator 3.5.1 - Managing priority of includes for code parsing
OmegaPhil at startmail.com
Mon Jan 25 22:07:07 CET 2016
On 25/01/16 10:50, Nikolai Kosjar wrote:
> On 01/22/2016 08:51 PM, OmegaPhil wrote:
>> I currently use Qt Creator as a code editor (not building etc) for a
>> number of codebases, via importing generic projects. Currently working
>> with the kernel code, I noticed that the default behaviour of code
>> parsing is to use the system kernel headers rather than those in the
>> Looking at the .includes file, all directories are present, however Qt
>> Creator still says it can't find some headers, and the ones it can find
>> come from /usr/include (by hovering over #include). Is there a way to
>> tell Qt Creator to prioritise the project includes?
> The includes in your <projectname>.includes shouldn't be ignored and
> this seems to work fine here with Qt Creator 3.5.1 and Qt Creator from
> the master branch.
> Note that the includes come from your project (*.includes) and the
> toolchain. Thus, "/usr/include" probably comes from the latter.
> You probably need to configure the right toolchain for your Kit. You
> also can set an invalid toolchain (e.g. a custom toolchain created with
> no compiler path) so only the include directories from the project's
> *.includes will be used.
Thanks - Qt Creator 3.6.0 here on Debian Testing - however I think Qt
Creator has just upgraded so the prior report was with 3.5.x.
I have made an invalid kit with no compiler specified, then restarted
the IDE and waited for all file parsing to complete - the results are
worse now (almost nothing is found) - I noticed string.h was being
detected in the tools/perf/utils/include/linux path, which is 'correct'
in that its coming from the source dump, but invalid as it should be
using include/linux/string.h - so I deleted all tools directories from
I recreated the kernel project again, however Qt Creator appeared to
hang on the 'finish' stage (>5 minutes with a core maxed), and now it
appears to get a third of the way through 'Loading Session' before it
dies (maxed core permanently). Oddly killing the UI does not cause the
underlying process to die, but that does respond to SIGTERM.
Something else to note, multiple parsing runs seem to cause insane
amounts of RAM to be used (e.g. >9GB), so it looks like the IDE isn't
freeing resources here.
Looks like the IDE doesn't cope well with large codebases?
I'll try to build v3.5 Qt Creator from source tomorrow and see if it
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: OpenPGP digital signature
More information about the Qt-creator