• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 80 subscribers
  • Views 339 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

MSP-TS430PN80A: Problem with Project with a Lot of Build Configurations

TI-CSC
Genius 16305 points

Part Number: MSP-TS430PN80A

Hello E2E Experts,

I have a project, imported from the previous Eclipse-based CCS, with a lot of build configurations that are a cross-product of 6 different hardware platforms and different customer specific configurations.

The issue I have is mainly that when I need to add or remove a file from many build configurations I have to do it one by one in the new CCS Theia, which is a slow and tedious process.

I tried reducing build configurations to just support the hardware platforms and have the customer defines injected when building from command line, but the ccs-server-cli does not support settings additional defines in its buildProject action.

Is there any way to either ease the setup of many build configurations using CCS or a way of building from command line each configuration injecting some defines? Or is there any other method recommended by TI for this case?

  • 0
    TI__Guru**** 485201 points

    Hello,

    TI-CSC said:
    Is there any way to either ease the setup of many build configurations using CCS or a way of building from command line each configuration injecting some defines? Or is there any other method recommended by TI for this case?

    One idea that came to mind was to leverage compiler command files (not to be confused with linker command filed (*.cmd). The idea to to have the project (and the relevant build configurations) reference the same command file in the compiler settings. Then if you want to add a compiler option to all configurations referencing the compiler command file, you can just add it directly to the command file once and it will apply to all relevant configurations. And any changes (add/remove/modify of options) to the file would again apply to all relevant build configurations. This command file is useful to not just manage multiple build configurations, but also multiple projects.

    See the compiler user's guide section 2.3.2 for more information on "cmd_file": https://www.ti.com/lit/ug/slau132y/slau132y.pdf

    Thanks

    ki

  • 0
    TI__Guru**** 485201 points
    TI-CSC said:
    imported from the previous Eclipse-based CCS

    Note that we are also looking to bring back the CCS Eclipse feature to select "all Configurations" when modifying build options. We can look to do this for a future CCS 20.x release.

  • 0 in reply to Ki
    TI__Guru**** 485201 points
    Ki said:
    Note that we are also looking to bring back the CCS Eclipse feature to select "all Configurations" when modifying build options. We can look to do this for a future CCS 20.x release.

    The tracking link for this effort is: https://sir.ext.ti.com/jira/browse/EXT_EP-13041

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 10 points

    Hi Ki,

    Thank you for your suggestions. For the feature that you will add in the guture, not only it is useful to mass-edit the compiler options, but also, outside the options, when excluding files from build, would be perfect for CCS to show a list of checkboxes, one per build configuration, so you can see where the file is currently excluded and you can edit easily where it should be. In Eclipse CCS it was this way, and I at least used it a lot.

    As for the cmd_file, it looks interesting but I would still need to have all combinations of build settings as different build configurations, and would still have the issue with excluding files for so many build configurations. It would be really nice if it were possible to inject this when using ccs-server-cli, so I would need a lot less build configurations and would introduce settings only from terminal mass build.

    Thank you and best regards,

  • 0 in reply to Sergio Blanco
    TI__Guru**** 485201 points
    Sergio Blanco said:
    In Eclipse CCS it was this way, and I at least used it a lot.

    Yes the goal is to bring back the CCS Eclipse behavior.

**Attention** This is a public forum