Console output of TouchGFX Environment messed up when compiling Simulator

[t.decker]

I have a running STM32F7 project with TouchGFX on a custom board. Now I need to create a MS Windows application where config files can be edited. I thought misusing the simulation.exe generated by TouchGFX might be a good way to go. Same user interface for the customer, export/import of config files via USB storage device.

Of course at the beginning the Simulator won't compile because it tries to include HAL and other stuff that needs to be excluded by #ifdef SIMULATOR and exchanged with custom code for the Windows application. My plan was to wipe out one mistake after the other by starting the compile process in the console over and over again. But the console output of the build process is really messed up when starting from the TouchGFX Environment console instead of clicking Run in the Designer and looking at the log window.

Any hints on how to fix the console output? It not only has wrong indentation, it is also mixed up text.

I'm using Win10 and TouchGFX 4.23.2

[t.decker · Accepted solution]

Just found out, that running the make with only one thread

make -f simulator/gcc/Makefile -j1

 "fixes" the problem. Might be slower, but at least I can read the output properly.

[Mohammad MORADI ESFAHANIASL]

Hello @t.decker ,

Glad to hear that you managed to fix the issue. We will investigate more on this issue.

Could you please select your comment as the accepted solution? 

[t.decker]

Hello @Mohammad MORADI ESFAHANIASL,

thank you for investigating this. Never seen this behaviour on any gcc compiles with -j[>1] before. I've also noticed that - while CubeIDE uses gcc 12 - the Windows application is built with a quite old gcc 7.3.

[Mohammad MORADI ESFAHANIASL]

Hello @t.decker ,

I asked a couple of my colleagues and they told me they have seen such an issue, and they used the same solution as yours to find out what the problem was. So, I haven't found an exact reason for it except that it can happen.

About the version of the gcc, we are considering updating to a newer version, but I cannot tell when it will happen. 

Best regards,