• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 52 subscribers
  • Views 536 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

In CCS 6.1 is there a way to maintain settings for Debug and Release configurations

Chester Gillon
Guru 92251 points
Other Parts Discussed in Thread: AM3352

When using CCS 6.1 is there a way to set the same project properties for both the Debug and Release configurations at the same time, e.g. when adding Include paths and libraries?

E.g. when linking a library created in a different CCS project in the workspace, the library file was referenced as "${WORKSPACE_LOC}/AM3352_SOM_platform/${ConfigName}/AM3352_SOM_platform.lib", making use of the ${ConfigName} variable, so that the same library file reference can be used for both Debug and Release platforms. However, when attempted to select a configuration of "[ All Configurations ]" I get the message that "Batch Operations are not supported":

This means that the settings have to be copied for both the Debug and Release configurations.

[I note that the stock Eclipse 3.6.1 in CentOS allows "[ All Configurations ]" to be used]

  • 0
    TI__Guru**** 173310 points

    Chester,

    Although this is allowed by stock Eclipse, the reason it is currently disabled in the CCS GUI is because CCS supports compiler tool versioning and build-options can look very different between different tool versions.

    However, it is not an unreasonable request, and in fact has already been requested internally and is being tracked under enhancement request # SDSCM00051541.

  • 0 in reply to AartiG
    Guru 92251 points

    AartiG said:
    Although this is allowed by stock Eclipse, the reason it is currently disabled in the CCS GUI is because CCS supports compiler tool versioning and build-options can look very different between different tool versions.

    Thanks for the explanation.

    I hadn't noticed before, but now realize that the "General" CCS Project Properties allow a different Compiler version to be used for each Configuration.