> > What is the best/designated way to supply relacement macros for those
> > symbols so the clang analysis succeeds? Is there some configuration/setting
> > in Qt Creator? Should I patch the code? Should I pass this to clang as
> > command line arguments?
>
> You should contribute the
Sorry for asking again... I have not found a solution yet.
I tried to define the macros using #ifdef __clang__ / #endif but it seems
__clang__ is not
defined during code model parser run. Also all GCC smybols are defined so I can
not
disinguish clang from GCC.
I also tried to add a -D argument
Hi!
I am using the new Clang Code Model in Qt Creator to highlight violations.
Recently I introduced some experimental C++20 functions in my code. These
functions are
integrated using a GCC header () that introduces
three
intrinsics that are unknown to clang:
__builtin_FILE()
