C/C++: Kalimba C Compiler not recognised

[bitpk1996]

Description of the issue

build_trace.log:
c:\qtil\adk_toolkit_1.2.9.25_x64\tools\kcc\bin\kcc.exe does not look like a compiler. If it is infact a compiler, please contact GitHub.
[E 12:28:25 12704] Not a compiler; exiting. Reason: --version stdout was:
Kalimba C Compiler, 32-bit, Version 2.20 (part of kcc version 76)
@(#)Based on CoSy release 1801, 2008
GNU assembler (GNU Binutils) 2.18 QTIL build 114-18849
klink (GNU Binutils) 2.18 QTIL build 114-18849

[hmakholm]

Thanks for reaching out.

Unfortunately CodeQL depends on understanding the command line to the C compiler such that it can know which environment to analyze the code under -- especially how to preprocess the code, e.g., where to find its system headers. Adding such knowledge about proprietary compilers for minor embedded architectures is not something we foresee having the engineering capacity to do soon.

Practically, your best bet for getting a CodeQL analysis of your codebase will be to somehow trick one of the compilers listed at https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/ into compiling it. The compiled code doesn't need to be able to run, so long as CodeQL can see a compiler be happy with it. You'll probably need to point at the Kalimba compiler's system headers, and possibly also write some headers with fake declarations of any Kalimba-specific intrinsics you depend on.

[bitpk1996]

Can you give me an example of how I can trick the compilers listed ？
I don't quite understand here :
You'll probably need to point at the Kalimba compiler's system headers, and possibly also write some headers with fake declarations of any Kalimba-specific intrinsics you depend on.

Practically, your best bet for getting a CodeQL analysis of your codebase will be to somehow trick one of the compilers listed at https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/ into compiling it. The compiled code doesn't need to be able to run, so long as CodeQL can see a compiler be happy with it. You'll probably need to point at the Kalimba compiler's system headers, and possibly also write some headers with fake declarations of any Kalimba-specific intrinsics you depend on.