• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 443 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/66AK2H12: Installing code composer studio as part of source control folder

Shiran Ben Israel
Intellectual 530 points

Part Number: 66AK2H12

Tool/software: Code Composer Studio

Hi

I would like to perform a headless build compilation of my ccs projects without having to install code composer on every single computer that needs to perform the compilation.

Therefore i would like to put a minimal installation inside my source control repository.

My current problem is with RTSC components (sys bios, xdc tool etc..), I cannot figure out where to define in the project (and not workspace) the relative location to these components.

I am currently using code composer 6.1.3 but I can upgrade

Sincerely

Shiran 

  • 0
    TI__Guru**** 476051 points

    Hello Shiran,

    Shiran Ben Israel said:
    My current problem is with RTSC components (sys bios, xdc tool etc..), I cannot figure out where to define in the project (and not workspace) the relative location to these components.

    The location of these products (RTSC, XDC, BIOS, etc) are stored in a file inside the CCS directory (.\ccsv6\eclipse\configuration\ccs.properties). When a new product is discovered by CCS, it will append to the list in the file and then be "known" to CCS. Hence, such information is not stored in the project as it is not necessary.

    ccs.properties is a text file and it can be modified manually to update the paths if you wish.

    Thanks

    ki