Borrar filtros
Borrar filtros

PSaYC: Select the Polyspace configuration language

1 visualización (últimos 30 días)
Oliver Müller
Oliver Müller el 2 de Mayo de 2022
Comentada: Oliver Müller el 3 de Mayo de 2022
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 comentarios
David Delarue
David Delarue el 2 de Mayo de 2022
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
Oliver Müller el 3 de Mayo de 2022
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!

Iniciar sesión para comentar.

Respuestas (0)

Productos


Versión

R2022a

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by