Execution time of polyspace-configure when using a compilation database file

I am currently in the phase of trying out Polyspace R2021b coming from R2019b. A major improvement would be to avoid the additional build for "polyspace-configure" listening on the build process output and use the "compile_commands.json" instead.

So i tried it out and also created a compiler configuration XML file (the documentation is lacking here i must say) for our custom compiler but to my suprise running "polyspace-configure" now takes ~5 min. so more time than the actual build takes. For every source file several steps are executed ("Importing definition of predefined macros", "Computing includes", ...) so i am wondering now if there is some configuration/usage problem or if this i how it is supposed to work.

[Christian Bard]

I would recommend Peter to contact Technical Support with the two zip associated with easy-debug information:

• one easy-debug w/ "standard" listenning build process of polyspace-configure
• one easy-debug w/ compile_commands.json process of polysapce-configure

See doc of option -easy-debug here: https://www.mathworks.com/help/bugfinder/ref/polyspaceconfigure.html#bt_t90b-optionvalue

[Peter Bauer]

Thanks for the reply, i opened a ticket as suggested. However, it would be helpful to have some documentation on how polyspace-configure is supposed to work with the compilation database input.

With the "standard" method there was no need for a compiler configuration file and the compiler was not executed so it did not have to be in the PATH. Then there are a lot of info, warning, ... messages that are not self-explanatory so its not clear if and what to do.

Answer 1

[Anirban]

Your compiler is actually invoked even when you use the JSON compilation database. But it is invoked to compile simple source files from Polyspace (behind the scenes) and not your actual project. The build command approach which compiles your actual project should take much longer. You can see the difference between the build command and compilation database approach here.

I am responding to this question just to clarify on your statement that the compiler is not executed at all. About the process taking longer with the compilation database compared to the build command, this is something to be looked into in further detail. For instance, the compilation database format might be interesting to look at. Hopefully, Technical Support was able to help you.

[Peter Bauer]

Thank you for pointing me to the documentation! I haven't received an answer yet, looking forward to it.