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.

CODECOMPOSER: Compiler version Validator error not shown in command line execution

Part Number: CODECOMPOSER

Hi,

When using Build Properties -> Validator in Code Composer Studio 10.3.1 to force a specific compiler version, if the specified compiler is not installed in the build machine the IDE shows an error in Console such as the following:

However, when I execute the following clean command in a command line, the command fails but the console doesn't show the cause of the error:

C:\User\ADO Agent\Work\58\s>eclipsec -noSplash -data "." -application com.ti.cc studio.apps.projectBuild -ccs.projects Board_level_test -ccs.clean

 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

 CCS headless build starting... [Mon Jun 14 18:03:08 CEST 2021]

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

 ================================================================================

 Pre processing...

 

===============================================================================

 Building...

 

================================================================================

 CCS headless build complete! 1 out of 1 projects have errors.

Is there any way to show that error in the console? The intention is to be able to show the error cause as part of a Continuous Integration Pipeline.

Thank you very much for your attention,

Álvaro

  • UPDATE:

    After more testing, I realize that doing a Project Clean in the CCS IDE does not generate the compiler version error. A Project Build action does.

    However, the above mentioned clean command executed in command line returns an error, without specifying what caused it.

  • A clean command would not invoke the compiler, hence the error would not get generated - regardless of if it was cleaned from the IDE or command line

    I suspect error mentioned from the command line clean command is an existing build error from before that was never resolved. Basically you tried to build the project, which resulted in an error and then that error was never cleared when you tried just cleaning it. It's the same as if you just run a clean project from the IDE after the build failure. The error is still there in the problems view.

    If you import a project to the workspace and then first try to clean it from the command line, the clean will be executed with no errors even if the required compiler version (with strict validation) is not available.

    Hope that clears things up.

    Thanks

  • Thank you very  much Ki, it is as you said.

    Where are this previous errors stored? I deleted the .metadata folder but I was still getting the same error...

  • It should be stored in the .metadata. The issue you are seeing is likely because when you import a project into the workspace (after cleaning the workspace), the validator will run. So the error would reappear

  • I see, thanks!