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.

CCS: C/C++ build "Stop on first build error" won't work

Tool/software: Code Composer Studio

Using am572x idk board with CCS 7.4 and pdk_am57xx_1_0_8, CCS spills out thousands of error when compiling a TI-RTOS C++ project. The project setting in C/C++ build "Behavior" tab is set as "Stop on first build error". The error is caused by no corresponding closing brace in "<ti/drv/emac/src/v4/emac_drv_v4.h>". Starting of line 40 in the "emac_drv_v4.h", 

#ifdef __cplusplus
extern "C" {
#endif

no corresponding closing brace in the header file.

Why the CCS keep going even so many errors encountered? The other weird thing is that the same project compiles with no error in Windows but fails in Linux, why?

Thanks for your attention. 

  • Karl,

    Would you mind sharing your project so we can reproduce this issue? If you do not wish to post it here you can zip it up and send it to me via private conversation.

  • Our project contains many proprietary info which I cannot share.
  • Karl Gu said:
    Why the CCS keep going even so many errors encountered?

    Are all those errors coming from the same source file? If so, that is expected behavior. Even if the "Stop on first build error" setting is enabled, it will still finish building the current source file and report all the errors found in that file, but it should not continue with building the other source files. Also if the "Enable parallel build" option is enabled (which it is, by default), then multiple source files may begin building at the same time, in which case the build will stop after all of those files are completed. You can try disabling the parallel build option to see how that impacts it. 

    Is this in line with the behavior you are seeing?

  • The errors are coming from two files. After disable parallel build, errors are coming from a single file. Thanks for the clarification.

    This does not explain why Windows version of CCS succeeded for the same project. BTW, I hope the closing brace could be added for next PDK release.
  • Karl Gu said:
    This does not explain why Windows version of CCS succeeded for the same project.

    Does the file in question have a .C extension? If so, it will be interpreted as either C source or C++ source depending on the operating system. Please refer to the section titled "Specifying Filenames" in the TI Compiler Users Guide. As a reference, the ARM compiler Users Guide can be found here.

    Karl Gu said:
    BTW, I hope the closing brace could be added for next PDK release.

    This should be fixed in a future release as per this thread.

  • .CPP extension
  • Hmm. I don't think I can explain it then without looking at a reproducible test case.
  • When I got some time, I hope I could create a simple project to reproduce this. Thanks