Does SonaQube buildwrapper support KeilC 8051 C51.exe and LX51.exe compiler?

SonarQube Server / Community Build
1

Hi SonarQube support,

I am using the build-wrapper, version 6.15 (win-x86-64) and trying to run code scan against with our 8051 projects, but I hit a problem to generate correspondent .jason file for sonar-scan to test with while using build-wrapper.
The bw log file shows that it will skip the C51.exe and LX51.exe process while wrapping, so this jason file is almost empty there,

// build-wrapper.log
//
Tue Aug 13 09:03:25 2024: build-wrapper, version 6.15 (win-x86-64)
Tue Aug 13 09:03:25 2024: isWow64: 0
Tue Aug 13 09:03:25 2024: windows version: 6.2, service pack: 0.0, build number: 9200, product type: 1
Tue Aug 13 09:03:25 2024: current directory: C:\sonar\src
Tue Aug 13 09:03:25 2024: command line received: <C:\Keil_v5\UV4\UV4.exe -b -j0 Kernel.uvproj>
Tue Aug 13 09:03:25 2024: initializing json file
Tue Aug 13 09:03:25 2024: starting debug cycle
Tue Aug 13 09:03:25 2024: process created with pid: 2052
Tue Aug 13 09:03:25 2024: image path name: <C:\Keil_v5\UV4\UV4.exe>
Tue Aug 13 09:03:25 2024: command line: <C:\Keil_v5\UV4\UV4.exe -b -j0 Kernel.uvproj>
Tue Aug 13 09:03:25 2024: working directory: <C:\sonar\src>
Tue Aug 13 09:03:25 2024: isWow64: 1
Tue Aug 13 09:03:25 2024: skipping process C:\Keil_v5\UV4\UV4.exe with pid: 2052
Tue Aug 13 09:03:27 2024: process created with pid: 22060
Tue Aug 13 09:03:27 2024: image path name: <c:\Keil\C51\BIN\C51.EXE>
Tue Aug 13 09:03:27 2024: command line: <“c:\Keil\C51\BIN\C51.EXE” @“.\output\main.__i”>
Tue Aug 13 09:03:27 2024: working directory: <C:\sonar\src>
Tue Aug 13 09:03:27 2024: isWow64: 1
Tue Aug 13 09:03:27 2024: skipping process c:\Keil\C51\BIN\C51.EXE with pid: 22060
Tue Aug 13 09:03:27 2024: process with pid 22060 exit with code: 0 (0x0)
Tue Aug 13 09:03:27 2024: process created with pid: 29068
Tue Aug 13 09:03:27 2024: image path name: <c:\Keil\C51\BIN\LX51.EXE>
Tue Aug 13 09:03:27 2024: command line: <“c:\Keil\C51\BIN\LX51.EXE” @“.\output..\kernel.lnp”>
Tue Aug 13 09:03:27 2024: working directory: <C:\sonar\src>
Tue Aug 13 09:03:27 2024: isWow64: 1
Tue Aug 13 09:03:27 2024: skipping process c:\Keil\C51\BIN\LX51.EXE with pid: 29068
Tue Aug 13 09:03:27 2024: process with pid 29068 exit with code: 0 (0x0)
Tue Aug 13 09:03:27 2024: process created with pid: 31948
Tue Aug 13 09:03:27 2024: image path name: <c:\Keil\C51\BIN\OHX51.EXE>
Tue Aug 13 09:03:27 2024: command line: <“c:\Keil\C51\BIN\OHX51.EXE” “.\output..\kernel” H386

Tue Aug 13 09:03:27 2024: working directory: <C:\sonar\src>
Tue Aug 13 09:03:27 2024: isWow64: 1
Tue Aug 13 09:03:27 2024: skipping process c:\Keil\C51\BIN\OHX51.EXE with pid: 31948
Tue Aug 13 09:03:27 2024: process with pid 31948 exit with code: 0 (0x0)
Tue Aug 13 09:03:28 2024: process with pid 2052 exit with code: 0 (0x0)
Tue Aug 13 09:03:28 2024: finalizing json file

Please help confirm the SonarQube support of this C51.exe and CX51.exe.

Thanks,

Hub

2

Hey there.

  • No, the build wrapper doesn’t support Keil C51. CPP-3408
  • v6.15 of the build wrapper was bundled with SonarQube v8.6. What version of SonarQube are you using? If it’s before v9.9, it’s EOL and you need to upgrade.
  • If you can upgrade to the latest version of SonarQube, v10.6, you can analyze your code using AutoConfig (no build wrapper or build required)
3

Hi Colin,

Thanks for your quick reply,
We have plan to upgrade to latest version, let me try the AutoConfig first,

Thanks,

Hub