This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCSTUDIO: CCS build console prints warning messages too slow

Part Number: CCSTUDIO

I'm using CCS to build a C project, and I find the build console prints warning messages too slow, which greatly increase the build time. The screenshot gif is in the attachment.

I've tried to use Windows cmd to execute the exact build command and found that the compiler itself was pretty fast. Is this a problem of CCS setting? How can I speed up the print speed?

  • Hello,

    If you build the same CCS project from the command-line using the headless project build command, do you see the same slowed output of messages?

    Thanks

    ki

  • The command-line headless build was slow too. But after using the command-line build, the CCS GUI became fast at first. It then slowed down again after printing lots of warning messages.

  • Thanks. What is the difference in performance? Like 50% slower? 

    What CCS version are you using?

  • It takes about a second to print a message. You can click the gif to see the real-time animation.

    With MISRAC option checked, there are usually hundreds of warnings, and many of them cannot be eliminated by modifying my code because it's about the most used library headers like stdint, stdbool, hal_stdtypes.

    My CCS version is 6.2.0.

  • f zl said:
    It takes about a second to print a message. You can click the gif to see the real-time animation.

    Sorry, I didn't realize the gif was animated. I see it now.

    One interesting thing. I noticed that when I use CCS 6.2.0 to build a source file with MISRA checking enabled, each message is outputted slowly like you described. When I import the same project into CCS 10.2.0 and build the same source file using the same compiler version, the messages are outputted much much faster. It is quite possible that optimizations were made to CCS in this area since CCSv6.2. Could you try using the latest CCS version and see if this helps in your case?

    Thanks

    ki

  • All right. Thank you.