When multiple main functions are detected, since Polyspace Code Prover has no knowledge of the application's architecture or intended build configuration, it cannot automatically determine which main function should be used as the entry point. That's why the analysis stops.
There are several reasons why a project may contain multiple main functions. For example, the source code may support multiple build targets, each with its own entry point, or it may include test harnesses and unit test code alongside the production application.
In such situations, it is the customer's responsibility to configure the project to have only one main in the analysis.
There are several ways to do so, depending on the situation.
For example, if there are files that are not part of the target application, such as test sources, they should be excluded from the analysis.
Another suggestion is to keep the mains but then to create modules (if Polyspace is used before R2026a) or projects in the Polyspace Platform UI.
If polyspace-configure is used to create the project, projects can be generated automatically to help structure the analysis: polyspace-configure Reference