VisualGDB 5 (r5): Embedded BSPs with mixed C/C++ code broken

[spkarjalainen]

Hi,

We have a custom BSP that contains a mix of both C and C++ files (C files for low level initialization etc, C++ for app and library code).

The “New Embedded Project” wizard/process in VisualGDB 5.0 (r5) appears to automatically convert ALL .c and .cpp files into either one or the other depending on what is selected in the “New Embedded Project” dialog (i.e. either “Generate a C file”, or “Generate a C++ file”). This was not the case with version 4.3 and earlier releases.

Is this a bug or expected behaviour? If expected, can a (say, checkbox) option be added that allows one to request that VisualGDB *not* override the extension of any source files from the BSP?

Regards,

Sam

[support]

Hi,

Normally the extra initialization code should be placed into a separate Embedded Framework, not into the sample.

If you absolutely need to make it a part of the sample, you can add the following element to the EmbeddedProjectSample element in the sample.xml file:

<DoNotUpgradeCToCpp>true</DoNotUpgradeCToCpp>

[Author]

Posts