• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 3301 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.

CCS/CODECOMPOSER: Environment variables

Ilija Pecelj
Prodigy 160 points
Part Number: CODECOMPOSER
Other Parts Discussed in Thread: CONTROLSUITE

Tool/software: Code Composer Studio

I am a bit confused with environment variables. As I understand, two types of variables exist 'path' used for referencing linked resources and build used during building/linking process. Those variables can be defined either at project or workspace level. Additionally, when I create a new project there seams to be several project variables predefined: CCS_BASE_ROOT, CCS_INSTALL_ROOT, CG_TOOL_ROOT to name a few (the list is not complete)....

Now comes the problem/confusion. I used dropbox to sync project between work/home computers. I declare several other variables for workspace level at home computer (e.g. CONTROL_SUITE_ROOT) with absolute path to controlSUITE. However when open the same project on the work computer, the CONTROL_SUITE_ROOT points to the location where control suite resides on the home computer, which is expected behavior. However, what confuses me is that CCS_BASE_ROOT, CCS_INSTALL_ROOT,CG_TOOL_ROOT point to the correct location (e.g at home computer cg tools are residing at d:\bin\ti\ccsv7..., while at work cg tools are in c:\ti\ccsv7...). So my question is how ccs populate those variables and where they reside? How can I define my own variables to be platform specific, that is to have different values for different systems?

Ilija

  • 0
    TI__Guru**** 421380 points

    Hello Ilija,

    Ilija Pecelj said:
    when I create a new project there seams to be several project variables predefined: CCS_BASE_ROOT, CCS_INSTALL_ROOT, CG_TOOL_ROOT to name a few (the list is not complete)....

    These are not actually project variables... meaning they are not stored at the project level. It is stored at the global workspace level. This is why the below happens: 

    Ilija Pecelj said:
    However, what confuses me is that CCS_BASE_ROOT, CCS_INSTALL_ROOT,CG_TOOL_ROOT point to the correct location (e.g at home computer cg tools are residing at d:\bin\ti\ccsv7..., while at work cg tools are in c:\ti\ccsv7...).

    Since it is tied to the global workspace level of your local CCS installation, it would point to the correct location for that local installation

    However, CONTROL_SUITE_ROOT is likely a project level variable. Meaning that the path to it is stored in the project metadata and would need be updated when the project is imported to a different environment. 

    What you may want to do is to remove CONTROL_SUITE_ROOT at the project level and then have a definition for it in at the workspace level for each environment (home and work). That way, you can just import the project and it should work like CCS_BASE_ROOT and the other internal global variables.

    See slide 22 of: http://software-dl.ti.com/ccs/esd/training/modules/portable_projects/sdoapps_mod_generic_ccsv6_portable-projects.pptx

    Thanks

    ki