Fix Build Errors from Non-C/C++ Files in Polyspace Platform User Interface

Issue

When you add source folders to a Polyspace^® Platform project, by default, files other than C and C++ files are not added to the project. However, when building the project, in certain cases, you might see errors related to non-C/C++ files.

For instance, suppose that your source folder contains a .y file that you do not use and that might contain errors. If you add this folder to a Polyspace Platform project and later build the project using a toolchain such as GNU gcc/g++ | gmake, the project build uses a generated makefile that is subject to implicit makefile rules. This makefile attempts to generate a .c file from the otherwise unused .y file in your source folder and might show any errors in these files. For more information on implicit makefile rules, see Catalogue of Built-In Rules.

Possible Solutions

To avoid the errors from non-C/C++ files, remove these files from the source folders if possible or use a toolchain that is not subject to implicit makefile rules.

Remove Non-C/C++ File from Source Folder

Remove the non-C/C++ files from your source folder if these files are not being used.

Use Another Toolchain

Use a toolchain such as GNU gcc/g++ | CMake/gmake that does not generate a makefile subject to implicit makefile rules. For more information on how to specify toolchains, see Compilation toolchain (Testing).