Running the scanner with the associated build-wrapper inputs is functional, no errors are raised by the scanner
Looking at the results in SonarQube, I see that actually the default C++ quality profile is being used instead of my custom made C quality profile
Running with verbose logs shows:
CFamily Code Quality and Security 6.18.0.29274 (cpp)
Declared extensions of language C were converted to sonar.lang.patterns.c : /*.c,/*.h
DEBUG: β<file_name>.cβ indexed with language βcβ
Sensor CFamily [cpp] seems to be running which is parsing all my c files
So, what I can conclude so far:
The source files are correctly parsed and attached to the βcβ language
For some reason, the cpp scanner is running and it uses the (only) default C++ quality profile instead of the default C quality profile which I created
Sorry, I canβt provide the output of the build wrapper due to legal issues, but what I can say is that I am using the arm-none-eabi-g++.exe compiler for compiling the source code, and yes, I see β-xβ and βc++β options in the build wrapper output.
So, itβs a kind of cross-compiling in using a c++ compiler on a c code, but those are the project constraints.
Is there any way around this, to force the usage of C-only quality profiles? As my code is pure C code, so if I would try to use a C++ quality profile I will get a lot of false errors, which do not apply on C code.