CODECOMPOSER: V20.2.0 API Build targets not working correctly

Steffen Fuchs

Part Number: CODECOMPOSER

Tool/software:

Hi,

we are using the CCS API (software-dl.ti.com/.../ccs_project-command-line-full-api-guide.html) in order to build our hexfile via a CI/CD pipeline.

Our Project has an Debug and Release build target. The script we are using is the following:

ccs-server-cli.sh -noSplash \
        -workspace "$CI_PROJECT_DIR/workspace" \
        -application com.ti.ccs.apps.projectImport \
        -ccs.location "$CI_PROJECT_DIR" \
        -ccs.copyIntoWorkspace true \
        -ccs.autoBuild true \
        -ccs.configurations Release

The line -ccs.configurations Release directs CCS to build the Release target.

The problem is that it always defaults to the Debug build target. The only solution we found so far is the delete the Debug build in CCS.

We also tried to use -ccs.defaultConfiguration Release but with the same result.

Can you please advise on how to select a specific target to build in a multi target project.

Thanks!

Best regards

Steffen

5 months ago

0 Ki 5 months ago

TI__Guru**** 472291 points

Hello Steffen,

Steffen Fuchs said:
The line -ccs.configurations Release directs CCS to build the Release target.

the parameter is -ccs.configuration (without the "s"). Can you try using that?

Thanks

0 Steffen Fuchs 5 months ago in reply to Ki

Intellectual 685 points

Hi Ki,

tried it with -ccs.configuration the whole time. Then I found out that the api guide state that it is with an "s" (https://software-dl.ti.com/ccs/esd/documents/users_guide_ccs_20.2.0/ccs_project-command-line-full-api-guide.html) and changed it. Same result. So I´ve tried both and none is working.

Is the API guide wrong?

Thanks!

Best regards

Steffen

0 Ki 5 months ago in reply to Steffen Fuchs

TI__Guru**** 472291 points

I tried this in CCS 20.2.0 on Ubuntu 22.04. The ccs.configuration parameter does seem to be respected:

What is the exact command being used on the command line that is failing?

0 Steffen Fuchs 5 months ago in reply to Ki

Intellectual 685 points

Hi Ki,

thanks for getting back to me! As I mentioned above the complete command is:

ccs-server-cli.sh -noSplash \
-workspace "$CI_PROJECT_DIR/workspace" \
-application com.ti.ccs.apps.projectImport \
-ccs.location "$CI_PROJECT_DIR" \
-ccs.copyIntoWorkspace true \
-ccs.autoBuild true \
-ccs.configurations Release

Could you check wether the problem is -application com.ti.ccs.apps.projectImport -> you are using -application com.ti.ccs.apps.buildProject. I`m also using -ccs.copyIntoWorkspace true

Thanks!

Best regards

Steffen

+1 Ki 5 months ago in reply to Steffen Fuchs

TI__Guru**** 472291 points

Steffen Fuchs said:
Could you check wether the problem is -application com.ti.ccs.apps.projectImport -> you are using -application com.ti.ccs.apps.buildProject.

Ah, sorry I missed this. I thought you were using buildProject. You are using importProject (or projectImport).

Steffen Fuchs said:
-ccs.configurations Release

This option does not apply to importProject. Hence it is being ignored.

0 Steffen Fuchs 5 months ago in reply to Ki

Intellectual 685 points

Thanks! I will test it. Maybe you should update your API docs?

Best regards

Steffen

0 Ki 5 months ago in reply to Steffen Fuchs

TI__Guru**** 472291 points

Steffen Fuchs said:
Maybe you should update your API docs?

I actually do not see where ccs.configurations is mentioned for importProject. Can you show me where?

0 Steffen Fuchs 5 months ago in reply to Ki

Intellectual 685 points

Sorry my bad... docs are fine

Code Composer Studio™︎

Code Composer Studio forum

CODECOMPOSER: V20.2.0 API Build targets not working correctly