Qt Creator Clang Code Model problems collection

thanks for adding your problem here. I think your specific problem can be turned in a report at bugreports.qt.io - as we already have a reproducible example. Would you mind doing that? (and adding a link here?)

Thanks!

Maxxii · wrote on 15 Apr 2019, 15:42

@aha_1980 Actually, I made a bug report even before making that thread ;) And then decided to ask on forums to be sure. It's here. I also added comment to this bug, noticing it is solved by turning off clang code model.

aha_1980 · wrote on 27 Apr 2019, 09:55

https://forum.qt.io/topic/102198/many-incomprehensible-errors looks like another candidate...

aha_1980 · wrote on 30 Apr 2019, 03:51

https://forum.qt.io/topic/102266/autocomplete-on-a-hello-world-basic-project-doesn-t-works/4

aha_1980 · wrote on 1 May 2019, 05:02

https://forum.qt.io/topic/102272/using-qt-project-code-with-earlier-versions/10 also looks like a candidate

aha_1980 · 21 May 2019, 05:08

And another one: https://forum.qt.io/topic/102999/strange-variable-has-incomplete-type-and-forward-declaration-of-qapplication-issues

aha_1980 · wrote on 21 May 2019, 05:00

And one more: https://forum.qt.io/topic/103006/linux-qtcreator-and-qt5-9-6-compiling-gnu-c-libraries

J.Hilk · 21 May 2019, 05:19

@aha_1980

And another one: https://forum.qt.io/topic/102999/strange-variable-has-incomplete-type-and-forward-declaration-of-qapplication-issues

oh! I run into that as well, didn't think about turning off the code model as potential solution.

I ended up forwarding a class instance pointer several levels up in the hierarchy ....

This is stupid.

aha_1980 · J J.Hilk 21 May 2019, 05:08

Hi @J.Hilk,

oh! I run into that as well, didn't think about turning off the code model as potential solution.

Well I don't think turning off the code model is a solution. But most of these problems collected here have in common, that Clang has parse problems in a header which then propagate in every file that is including the header.

Tracking down these problems, however, is a tedious task.

aha_1980 · 7 Oct 2019, 04:08

https://forum.qt.io/topic/103030/qt-creator-4-9-0-can-t-disable-line-annotations-ignores-option

aha_1980 · wrote on 7 Oct 2019, 04:08

probably https://forum.qt.io/topic/107498/code-completion-is-not-working-in-qtcreator too

A.A.SEZEN · wrote on 7 Oct 2019, 04:48

probably
https://forum.qt.io/topic/107332/undeclared-i̇dentifier-ve-auto-complete-problemi/2
too.

rsacchettini · 28 Jan 2020, 05:50

Hitting a similar issue in Qtcreatorv4.11.0 on linux x64 ubuntu18 lts with CMAKE and gcc or clang btw, the symbols parsing i.e. finding functions or type definitions does not work :

does not work at all if not starting qtCreator in the actual CMAKE project source directory
Always stops working regardless after a few minutes to about 1hours, requires a restart of Qtcreator after which it usually works again.

Make me hate trying to convince my colleagues to migrate from Eclipse to QtCreator, I was always telling them how much more usable and snappy QtCreator is but a bug like this is not a small bug and not a good look to my colleagues currently trying it.

Regards

aha_1980 · wrote on 28 Jan 2020, 05:50

Hi @rsacchettini,

Clang is a double-sided sword. If it works, it gives you fantastic insight in your code - but if not, you often have no idea why.

I'd recommend you nevertheless to start an own discussion topic here, we might be able to help you get it at least running. Can you at least work on a small example project?

Also note that the CMake integration is in flow currently, so there might be regressions in .0 releases. You might want to try the last stable or the next snapshot release.

Regards

Edit: Ah, you alread did: https://forum.qt.io/topic/111067/symbols-parsing-and-finding-stops-working-qtcreator-v4-11-0-cmake-on-linux-x64

Neil9 · wrote on 2 Dec 2021, 03:36

When I just typed a few code in a c++ project,I got an error in the editor which was " no member named 'uint64_t' in namespace 'std' ".The code are listed here:

#include <iostream>
#include <cstdint>
using std::uint64_t

I didn't think it was the code made the issue.And I didn't know how to fix it until I found this topic.Actually,I solved the problem just by disabling Clang. It was really useful.