Evgueni Driouk

@AncaOprea11 , I have noticed a strange thing in the stack trace: if a mimi.rteconfig would not exist, it the exception would be thrown prior to com.arm.cmsis.pack.project.RteProjectUpdater.collectErrors() call. Could you...

That is correct behavior by design. A newer pack is installed, but there is no change in the *.rteconfig file itself. Pack information represents a hint which pack was used...

Hi Sergio, we considered possibility to have separate/shared RTE configurations for each CDT build configuration from the very beginning. We have decided then to use single configuration due to complexity...

Thank you for the detailed problem description. Obviously we have never tested such scenario. Could you suggest a fix for this issue? Pull request is very velcomed. ~ Evgueni

No, that is currently not possible

Maybe, but not in the near future. The major problem is project management that is currently based on Eclipse CDT.

An experimental import of csolution-build projects is added to 2.10.0. Executable and all source files are imported into a "C/C++ Executable" CDT project. This allows to debug projects built with...

We need to investigate why it has been done. As far as I remember it was not the extent calculation, but a JFace drawing problem on one of the platforms....

We have had the similar problems with SWTBot and solved the problem by modifying tests.