Hi @itaymov,
Your log file contained interesting information:
08:56:32.457 DEBUG: Probing compiler: [ccache, /opt/toolchains/Intel-Puma-Toolchain_03/usr/bin/armeb-buildroot-linux-uclibcgnueabi-gcc, -x, c, -mthumb, -v, -dM, -E, -]
08:56:32.480 DEBUG: stdout:
08:56:32.480 DEBUG: stderr:
execv: No such file or directory
08:56:32.481 WARN: Invalid probe found, skip analysis of files: [/home/itay/dev/SamDaemon/ninja-puma6-86nOSp/../compat.c]
The compiler probe 'stdout' is expected to contain at least one '#define' directive:
Once we read data from the compilation database, we try to probe the compiler you use to get additional configuration from it, and this is the step that is failing for you.
There could be different reasons for that, but I think the most probable is that you have the same issue that is described in this other post: Even if you have the full path to the compiler, you only have a relative path to ccache.
Since ccache is just an extra layer which is not useful here, could you please try to preprocess you compilation database so that lines like:
"command": "ccache /opt/toolchains/Intel-Puma-Toolchain_03/usr/bin/armeb-buildroot-linux-uclibcgnueabi-gcc -Idc@exe -I. -I.. -I../include.....
Are replace by:
"command": "/opt/toolchains/Intel-Puma-Toolchain_03/usr/bin/armeb-buildroot-linux-uclibcgnueabi-gcc -Idc@exe -I. -I.. -I../include
(an alternative would be to put the full path to ccache on every line)
Let me know if this works for you!
Since this situation is not really user friendly, I created a ticket to try and improve it.