• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 322 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 5.1 RC1 - resource globals not resolved

Alexander Stohr
Expert 1200 points

self defined variables like "MY_PACKAGE_ROOT" in the resources section wont get honoured and resolved in the project export and XDC creation stage.

instead some warnings on exactly the defined variables will pop up plus replacements with an empty expression.

this is most probably a problem of this revision since former revisions just worked with the very same project setup.

i doubt its the import filter since basically all looks fine in the GUI - only at export times the problem gets visible.

 

 

 

 

 

 

 

 

 

  • 0
    TI__Guru**** 480941 points

    Hello,

    Could you provide more details? Is "MY_PACKAGE_ROOT" an environment variable that used to get picked up in previous CCS versions but not 5.1RC? What do you mean by "project export"?

    Thanks

    ki

  • 0 in reply to Ki
    Expert 1200 points

    the project file is edited and then saved in CCS. then its finally handed over from CCS to XDC at some certain point in time - thats what i meant with "export".

    that variable name was a generic user sample. go to the project settings and visit "Resource" -> "Linked Resources" -> Tab "Path Variables" -> "Name/Value". There you will find a few standard settings with options to add custom settings. Existing standard names are: CCS_BASE_ROOT, CCS_INSTALL_ROOT, ...

    If you add custom/own entries there then you will find them honoured in earlier builds of CCS but no longer in the current RC.