On 6/3/21 11:23 AM, Daniel Brunner wrote:
I tried setting the diagnostic configuration but this didnt change
anything,
still no warnings/errors shown (besides those from cppcheck, but thats
a different plugin).
I also tried running qtcreator with the environment variable
QTC_CLANG_CMD_OPTIONS_BLACKLIST="-mlongcalls;-fstrict-volatile-bitfields;-fstack-reuse=all;--target=xtensa-esp32-elf"
this removed the errors in clang-tidy for the first 3 failed
arguments, but the last one for the target architecture stays.
Anything else I could try?
Let's not mix different topics, that will just confuse things.
Your original problem was that the code model failed to parse your
project; is this still the case after changing the setting as discussed
earlier? clang-tidy errors are are a different issue.
Christian
Am Di., 1. Juni 2021 um 10:39 Uhr schrieb Christian Kandeler
<christian.kande...@qt.io <mailto:christian.kande...@qt.io>>:
On 5/31/21 4:24 PM, Daniel Brunner wrote:
> I haven't seen any source file where autocompletion works. The
verbose
> console output is always similar or the same.
>
I assume in Tools->Options->C++->Code Model->Diagnostic
Configuration,
"Use diagnostic flags from build system" is enabled? What happens
when
you uncheck it?
Christian
_______________________________________________
Qt-creator mailing list
Qt-creator@qt-project.org <mailto:Qt-creator@qt-project.org>
https://lists.qt-project.org/listinfo/qt-creator
<https://lists.qt-project.org/listinfo/qt-creator>
_______________________________________________
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator
