build wrapper windows x64
I have a embedded project consisting of three modules. Each of the module is compilable separately. But together they create a firmware. The sources are in C/C++. The compiler used is arm-none-eabi-g++ or arm-none-eabi-gcc version 7.3.1.
My problem is, that sonar-scanner does not see sonar.cfamily.build-wrapper-output parameter in module’s sonar-project.properties file.
I have compiled one of the modules (with build wrapper eavesdropping) and gathered defines, etc. and saved it to root/module1/res/sonarqube/bw_output. Generation was successfull.
Althoug it says:
when I am using arm-none-eabi-gcc. And what’s up with double slashes?
Then I save this path to modules sonar-project file as:
The properties file is saved to root/module1 directory
In main properties file (root/sonar-project.properties) I state I have one module (just for start):
After I run the scanner I can see that the module’s properties file is seen - because of source files found using sonar.sources=src. But it’s unable to see sonar.cfamily.build-wrapper-output.
I also trier do save output to module’s folder.
Only way to make this work so far is to save this property to main sonar-project.properties, but that is not a solution for me - I have to have separate modules with separate defines, etc.
My questions are following:
Why cannot sonar scanner see sonar.cfamily.build-wrapper-output in module’s properties file?
Why is there clang instead of GCC in BW’s output?
Isn’t it wrong to have double slashes in BW’s output?