• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 55 subscribers
  • Views 877 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: Move compilers from CCSv7 to CCSv8?

twelve12pm
Genius 4455 points

Tool/software: Code Composer Studio

I have two installations of CCS on my system: CCSv7 and CCSv8.

I would like to uninstall CCSv7.

Before I do that: In CCSv7, I have several older compilers installed that I don't have in CCSv8, including: gcc-arm-none-eabi-6-2017-q1-update and ti-cgt-arm_16.9.8.LTS.

Is it possible to just move those directories from C:\ti\ccsv7\tools\compiler to C:\ti\ccsv8\tools\compiler prior to uninstalling CCSv7? Would these compilers be recognized by CCSv8?

  • 0
    TI__Guru**** 163035 points
    Yes in general that will work fine. CCS should automatically discover them the next time it starts up. If it does not you can go into the Preferences dialog and force it to rediscover under Code Composer Studio -> Build -> Compilers

    Regards,
    John
  • 0 in reply to JohnS
    Genius 4455 points
    Thank you. This worked.
  • 0 in reply to twelve12pm
    TI__Guru**** 163035 points
    Going forward as we release new versions of CCS you could keep copying the compilers between versions or if you like create a folder outside of CCS that has them and just setup that folder in the discovery path. I need to have multiple installs so I generally setup a common folder for compiler installs and then share them between CCS versions.

    Regards,
    John
  • 0 in reply to JohnS
    Genius 4455 points

    JohnS said:
    Going forward as we release new versions of CCS you could keep copying the compilers between versions or if you like create a folder outside of CCS that has them and just setup that folder in the discovery path. I need to have multiple installs so I generally setup a common folder for compiler installs and then share them between CCS versions.

    That is a good idea! Thank you for mentioning that.

    How do you handle CCS installing updates to compilers? Does it install under the CCS directory and then you move it to your common folder?

  • 0 in reply to twelve12pm
    TI__Guru**** 163035 points
    CCS installs them under ccsv8/tools/compiler

    Often I just end up copying them to /ti

    You can also download them from the compiler download page and then it will let you install them where you want and CCS will discover them afterwards as long as the path is in the discover path.
    www.ti.com/.../download.html


    Regards,
    John
  • 0 in reply to JohnS
    Intellectual 480 points

    I just want to inform you about a kind of misbehaviour that i was encountering.
    I have installed the compilers and products in a separat folder to be able to switch between ccs installations and try new ones. See the attached screenshot.

    It appears if a new compiler version is available and i install it to the compiler directory teh ccs is finding it and it is used during build.

    But there is still appearing an software update notification for the already installed compiler version.

    If follow the compiler, then it is installed inside the ccs installation folder. ccs already recognized this version in my compiler folder and should skip this update notice.

    It would be nice if you can give me some feedback.

    Bernhard

  • 0 in reply to Bernhard Seiz
    TI__Guru**** 163035 points
    Bernhard,

    I am not aware of a way to avoid what you are seeing short of disabling the compiler update site in CCS. The update notification is all based around Eclipse features. When installing a compiler via the update mechanism we install a "feature" into eclipse. For compilers outside of the CCS installation the Eclipse feature is not being installed so as far as Eclipse is concerned it is not there. The CCS compiler discovery mechanism works independently of this. To resolve the 2 we would need to do something where when we discover a compiler that we also install the feature to keep Eclipse in sync. That would also require the compiler folder to contain the required feature which I do not believe they currently do. I am currently out of the office but when I get back I can bring this up and see if there is something we could do.

    Regards,
    John