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.

Compiler Discovery Path Doesn't Propagate Into Subfolders

Other Parts Discussed in Thread: CCSTUDIO, SYSCONFIG

Hello,

Minor UI problems.

(a) I have been using CCSTUDIO 12.1 and want to upgrade to CCS 12.3 but still use the compiler that comes with CCS 12.1 (v2.1.2.LTS).

Using the existing tool discovery path 'C:/ti/ccs1230' as a template, compiler discovery does not work for the equivalent path 'C:/ti/ccs1210':

Eventually I found that explicitly adding the compiler path will add the old compiler:

It's not much of a discovery if I have to specify the path explicitly.

(b) After manual installation of the bundled SysConfig 1.14.0 from CCS12.1, the path shown is the path to the standalone version:

(c) Cannot remove incorrectly installed standalone SysConfig 1.14.0. Uninstall button greyed out.

  • The compiler/product discovery seems to have different rules regarding how deep to search in subdirectories depending on the path. It is a bit befuddling to me about it. I'll need to follow up with engineering regarding what the exact rules are.

  • I did check up with engineering and there are different rules depending on the path. The two "special" paths are C:\ti and the location of the compiler directory in the CCS installation. C:\ti is visible in the discovery list and CCS will search in subfolders up to 2 levels down in C:\ti. CCS will always also look in its own <CCS INSTALL DIR>\ccs\tools\compiler folder. For all other paths, it will only look for compilers (and other discoverable products) in that specific path and will not look in subfolders. 

    Hope this helps

    ki

  • Thanks Ki. At least I know the rules now.

    What about (b) and (c) please?

  • (b) After manual installation of the bundled SysConfig 1.14.0 from CCS12.1, the path shown is the path to the standalone version:

    You can only have one instance of a version discovered. Since the standalone version of 1.14.0 has already been discovered, the one from CCS 12.1.0 will be ignored.

    (c) Cannot remove incorrectly installed standalone SysConfig 1.14.0. Uninstall button greyed out.

    the Uninstall button only applied to some old legacy products that supported such functionality. Any relatively recent product uses a new format and the Uninstall option would not apply to it.

    If you want to remove it from the list of discovered products, you'll need to move the one you don't want discovered.