Our project builds with make.
There is a top-level make the calls makes within the subirs.
I tried the build-wrapper-linux-x86-64 … at the top level
Here is the top level make command I used:
build-wrapper-linux-x86-64 --out-dir /opt/git/etm/appliance/bwod/ make
The build completed under build-wrapper-linux-x86-64.
Lots of data in the build-wrapper.log file.
Nothing in the build-wrapper-dump.json.
An empty .json causes sonar-scanner to warn and exit.
I also tried integrating the build-wrapper-linux-x86-64 … into my make files so that it ran at each level. Doing that caused the build-wrapper.log and build-wrapper-dump.json files to get reset for each sub-make (which makes sense)
At one point the docs had me download a cfamily jar file. Where does that go?
The problem appears to come from your compiler executables being gcc47 and g++47, which are not recognized as standard executable names for gcc and g++. Thus the execution of the compiler is never recognized as your build is observed and the build-wrapper doesn’t capture any results.
It would work if your compiler executables were named with a dash, e.g. gcc-47 and g++-47, which is a more typical naming convention for having multiple versions of gcc on a linux system. Is there any chance you can rename the executables or use a symbolic link to make this adjustment?