Dear all,
the linter-clang is not recognizing the header files when they're included as "SYSTEM".
The issue can be reproduced with the attached example, that generates a compile_commands.json file.
In this example I include the directories using the SYSTEM flag. Doing so, the header file is included with:
-isystem include
However, as written in the doc, linter-clang searches for the directory include (preceded by a space), which ultimately result in linter-clang not finding the header.
On the other hand, everything works as expected when removing the SYSTEM flag, since in that case the compile_commands.json file reads:
-Iinclude
(with no space).
Would it be possible to add a protection, removing the leading space of a path when the flag -isystem is found?
Dear all, the linter-clang is not recognizing the header files when they're included as "SYSTEM". The issue can be reproduced with the attached example, that generates a compile_commands.json file. In this example I include the directories using the SYSTEM flag. Doing so, the header file is included with:
-isystem includeHowever, as written in the doc, linter-clang searches for the directoryinclude(preceded by a space), which ultimately result in linter-clang not finding the header. On the other hand, everything works as expected when removing the SYSTEM flag, since in that case the compile_commands.json file reads:-Iinclude(with no space).Would it be possible to add a protection, removing the leading space of a path when the flag
-isystemis found?Thanks in advance, best regards, Diego
linter_clang_example.zip