PSaYC: Select the Polyspace configuration language

Oliver Müller

2022 5 2

0 个回答

2 次查看（30 天）

0 个投票

After updating the Polyspace Access and subsequently Polyspace as You Code Version from R2021b to R2022a I get those popups from the Eclipse integration a lot:

Is there a way to tell the Tool that it will always be C?

2 个评论
显示无隐藏无

David Delarue 2022-5-2

The plugin requires a C/C++ project and expects to find a '.cproject' file in the project folder to detect automatically the language.

This dialog should only be displayed if no '.cproject' file is found. I've found no way to bypass the check except by creating manually this file... but i don't know which impacts it can have on the Eclipse IDE.

Are you using a C/C++ Eclipse project (if yes the .cproject file should already exist)?

Oliver Müller 2022-5-3

I have a non C main project with two C-type subprojects because I use a trustzone enabled controller. Some shared headers are in that projects context and that's from where I got those popups apparently.

I also have some projects which I only defined for Polyspace analysis because they are normally managed in an unsupported IDE (atmel studio which uses an older VS version as the base) so I didn't really care about project type there.

For all the workaround of adding an empty .cproject file works!

请先登录，再进行评论。

请先登录，再回答此问题。

Follow Question