Bug report: TouchGFX generates .cproject using spaces, CubeMX uses tabs

Tuoman · ‎2020-12-02

This will result to version control to annoyingly showing the whole file as changed when you use both generation tools now and then.

Please fix either CubeMX or TouchGFX to use same format? Thanks!

Khouloud OTHMAN · ‎2020-12-02

Hello Tuoman,

Thanks for your feedback, but the problem doesn't seem very clear. Could you please precise the scenario you have reproduced ? Which MCU are you working with and what version of CubeMX are you using?

It will be helpful to investigate the root cause of the problem.

I will be waiting for your response.

Thanks in advance,

Khouloud.

Tuoman · ‎2020-12-03

>Thanks for your feedback, but the problem doesn't seem very clear. Could you please precise the scenario you have reproduced ?

Create TouchGFX project in CubeMX
Open TouchGFX project (.touchgfx file in the project folder)
Click Generate Code
TouchGFX will generate .cproject file using spaces
Open CubeMX project (.ioc file in the project folder)
Generate Code in CubeMX
CubeMX will generate .cproject file using tabs, showing in version control that 100% of lines have changed, even without any changes

>Which MCU are you working with and what version of CubeMX are you using?

CubeMX 6.1.0, STM32H7B3. This should not have anything to do with specific MCU.

Issue seems quite clear to me. TouchGFX and CubeMX both generate code to the same .cproject file. However, CubeMX generates the .cproject using tabs when generated using CubeMX, and TouchGFX generates the .cproject using spaces when generated with TouchGFX.

This is annoying for version control, when it always overrides the whole file when nothing is actually changed in the .cproject file.

And there is no reason that other generator uses spaces, and the other generator uses tabs. Choose one or another for both.

Khouloud OTHMAN · ‎2020-12-03

Hi Tuoman,

Thanks for this detailed description. I have reported your request internally to be reviewed and fixed.

I will keep posted.

Thank you for your contribution,

Khouloud.