scan-build is a different analyzer: it needs to know how to compile each specific project to analyze them. We need to improve our heuristics on how to find out how to compile each specific project and exit in a cleaner way when it does not find a way.
See util/dockerfiles/clang-analyzer/run-analysis.sh
Metadata Update from @davidcarlos: - Issue tagged with: Enhancement
@fabio1079 you was working on this issue, what is the status?
Metadata Update from @davidcarlos: - Issue assigned to fabio1079 - Issue set to the milestone: version 0.4
There was a change at some point where we stopped passing the uncompressed sources path to the containers (we used to do that in earlier version of kiskadee). Then, we forgot to change the clang-analyzer container as well.
clang-analyzer needs to build a project to analyze it during the build step. This means that we need to be inside the project root directory. Since we do not pass this directory to the containers anymore, the current clang-analyzer container is broken and will never analyze anything: Since we do not enter the target project root directory, we end up with a container looking for a Makefile or a configure file in the tempdir where we extracted the source code.
We want to figure out the root path of the extracted directory and cd in there instead of doing cd $1 as we current have in the entry point code.
cd $1
Note that the cd $1 os legacy code for entering the directory kiskadee analyzers module used to pass to this container.
Metadata Update from @athoscr: - Issue untagged with: Enhancement - Issue tagged with: Bug
Metadata Update from @davidcarlos: - Assignee reset - Issue set to the milestone: None (was: version 0.4)