My build process involves uVision running a DOS batch file to perform various operations prior to compilation. The batch file contains various "echo" statements to indicate progress. However, these do not appear in the Build Output window until after the batch file has completed. I would like them to appear as and when they are encountered in the batch file. It seems that output is buffered up by uVision and flushed to the Build Output window at the end. Is there a way to change this behaviour?
Assuming this is for a Arm based device, and using the Keil MDK tools are installed at C:\Keil_v5\
A few quick suggestions:
1) FYI their is a CMSIS-Build standard:
The CMSIS-Build scripts might already be doing what you need:
Might be worth checking out.
2) there is a C:\Keil_v5\UV4\uVision.com that you could call instead of UV4.exe that will redirect the output into the DOS window
Hi, through my test here I can reproduce this issue. For now I'm not sure if this is implemented in this way on purpose in uVision or if there is any windows command that can autoflush the stdout somehow.
I would suggest you to open a support case via https://www2.keil.com/support/silver?P=&V=&S= , so that we can make a further check.
Hi there, was there a solution for this? I have the same issue.
Hi, no solution. I raised a support case and was told that "based on the feedback from our development team, we won't change/improve this behaviour."