• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 54 subscribers
  • Views 520 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.

CODECOMPOSER: How can I get the compiler and SDK version from command line?

Alvaro Muro
Prodigy 235 points
Part Number: CODECOMPOSER
Other Parts Discussed in Thread: CCSTUDIO

Hi,

I am preparing a Continuous Integration pipeline using Code Composer Studio 10.1.0 and 20.2.1.LTS compiler version and I want it to to ensure that all developers are usinig the same tools to generate the FW image, by checking:

- the version of the Compiler

- the SDK version

Is there a command to get theses two values from command line, or should I parse the .ccsproject file which contains both values?

Many thanks,

Álvaro

  • +1
    TI__Guru**** 421520 points

    Hello,

    Try using the below command:

    <CCS INSTALL DIR>/ccs/eclipse/eclipsec -nosplash -data <workspace> -application com.ti.ccstudio.apps.inspect -ccs.projects:externalResources <project name>

    The above command is for Windows. If on Linux, call 'eclipse' instead of 'eclipsec'. If on macOS, call 'ccstudio' instead.

    This command should give you all the dependencies for the project.

    ki

  • +1
    Guru 92251 points
    Alvaro Muro said:
    I am preparing a Continuous Integration pipeline using Code Composer Studio 10.1.0 and 20.2.1.LTS compiler version and I want it to to ensure that all developers are usinig the same tools to generate the FW image, by checking

    Rather than checking which version of the tools are in use by each developer, perhaps the Validator in the Build Properties could be used for force the tool versions used by each developer.

  • 0 in reply to Ki
    Prodigy 235 points

    Thanks Ki!

  • 0 in reply to Chester Gillon
    Prodigy 235 points

    Thanks Chester, I think I will use this option and save the parsing

  • 0 in reply to Chester Gillon
    Prodigy 235 points

    Hi again,

    I configured the Build validator but I haven't been able to see in which code composer file is this change stored. I see the versions are shown in .ccsproject file, but not the validator options, and this file and also .cproject file don't change when I change this options.

    In which file is this configuration stored? Is it stored at Workspace level in .jxbrowser-data or .metadata folders?

    The reason why this is needed is to understand how the Validator works and to be able to share this configuration with the rest of the development team, pushing it into the repository where we store our projects.

    Many thanks in advance,

    Álvaro

  • +1 in reply to Alvaro Muro
    TI__Guru**** 421520 points

    Hello,

    Alvaro Muro said:
    In which file is this configuration stored? Is it stored at Workspace level in .jxbrowser-data or .metadata folders?

    It is actually in the .settings folder. A file called "com.ti.ccstudio.project.core.prefs" will be generated that contains those settings

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 235 points

    Thank you very much Ki. I can see it.

    I am having an issue with the .ccsproject file, when I change the compiler version in the project build properties, the .ccsproject file doesn't get updated to the new version, I always see the original one it had when the project was created.

    I just tested this importing an empty project from resource Explorer.

    Is the .ccsproject file supposed to show the current configured compiler version?

    P.D: (Should I start a new question with this topic or is it OK to continue here?)

    Thanks

  • +1 in reply to Alvaro Muro
    TI__Guru**** 421520 points
    Alvaro Muro said:
    Is the .ccsproject file supposed to show the current configured compiler version?

    It actually shows the original project settings. Any changes made would actually be reflected in the .cproject.

    Alvaro Muro said:
    P.D: (Should I start a new question with this topic or is it OK to continue here?)

    In the future, please start a new thread if the question is unrelated to original thread subject.

    Thanks

    ki