MATLAB: Doesn’t polyspace-configure recognize the compiler in the custom configuration

armbugcodefinderheaderincludepolyspacePolyspace Bug Finderproversourceti

I am using polyspace-configure in combination with a Makefile to create a polyspace configuration for the TI ARM compiler as shown below:
polyspace-configure -prog myProject make -B targetName buildOptions
However, when I run this command, I see the following error message:
polyspace-configure: 7s: ERROR: All programs detected are unknown: there is no matching compiler configuration. Executed programs are: 
polyspace-configure: 7s: ERROR: armar        /opt/ti/ccs/tools/compiler/ti-cgt-arm_20.2.1.LTS/bin/armar
polyspace-configure: 7s: ERROR: armcl        /opt/ti/ccs/tools/compiler/ti-cgt-arm_20.2.1.LTS/bin/armcl
polyspace-configure: 7s: ERROR: bash        /bin/bash      
polyspace-configure: 7s: ERROR: build.sh      /tmp/polyspace_configure_tmp-e3ba-d09c/build.sh
polyspace-configure: 7s: ERROR: cmake        /usr/local/bin/cmake
polyspace-configure: 7s: ERROR: make        /usr/bin/make    
polyspace-configure: 7s: ERROR: sh         /bin/bash      
polyspace-configure: 7s: ERROR: The following compilers are recognized by polyspace-configure (with path to associated configuration files):
.
.
.
.
.
polyspace-configure: 7s: ERROR: No compilation unit detected in your build.
  Possible sources for this error are:
 - Your build command does not compile any C/C++ files.
 - Your compiler was not called. You must force a clean rebuild.
 - Your compiler is unknown to Polyspace. You must write a compiler configuration.
 - You use a compiler cache (such as ccache). You must deactivate it.
 - You use a distributed build system (such as distmake). You must deactivate it.
 - You use a -include-sources/-exclude-sources combination that filters out every source file. Consider setting -print-included-files and -print-excluded-files.
polyspace-configure: 7s: ERROR: Fatal error
How can I work around this error to continue with code verification?

Best Answer

This issue may have several different causes. As described in the error message, first ensure that there is no compiler cache in use, that the build is a clean build (first delete all build artifacts), etc. If those solutions do not work, try the following:
Manually enter the C and header files in Bug Finder, as shown here:
https://www.mathworks.com/help/releases/R2020a/codeprover/ug/polyspace-configure-source-files-selection-syntax.html
Because Bug Finder does not invoke the compiler itself, there will be no issue with recognizing a potentially unsupported compiler or toolchain. You can find all files with a Unix command like the following:
$ find . -name "*.h" -or -name "*.c"
Related Question