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

CCS: Is it possible to disable the automatic selection of a compatible compiler version in CCS?

Butters
Expert 2021 points


Tool/software: Code Composer Studio

Hello, my question is concerning the behavior of CCS when the compiler version specified in a project is not currently installed. The following screenshot shows how the "CCS General" project properties appear in this situation.

In an effort to prevent multiple developers from inadvertently using different versions of TI tools, I would much rather have it be an error if the exact version of the compiler specified in the CCS project is not installed. Is there any way to accomplish this? I've looked through a number of CCS/eclipse settings (including advanced ones) and haven't been able to find anything.

Thanks in advance,
Dave

  • 0
    TI__Guru**** 171309 points
    Dave,

    I couldn't find a way to do any of the things you mentioned: both disabling the automatic selection of a compiler as well as the criticality of the error message thrown. I filed the enhancement CCSIDE-3029 to put this forward for discussion (in about 1/2 hour you can check its status in the link SDOWP in my signature below).

    One additional idea is to have a specific "frozen" environment to be distributed to the developers. Something discussed in the page below:
    processors.wiki.ti.com/.../Enterprise_distribution

    Hope this helps,
    Rafael
  • 0 in reply to desouza
    Expert 2021 points
    Rafael,

    Thank you for looking into this, and for creating the SDOWP issue to consider this enhancement. Our developers do use something very similar to the "frozen environment" concept, but sometimes individuals still end up modifying their locally installed compiler versions after the fact (perhaps inadvertently). So while the frozen environment is an important starting point, CCSIDE-3029 would provide a final "sanity check" to make sure that the expected versions of the tools are used.

    I'm going to mark this post as resolved, and hopefully after your internal discussion TI will decide to pursue implementation of CCSIDE-3029.

    Thanks again,
    Dave