• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 461 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.

Path Variable shows as blank CCS5.4

David Sabol
Genius 4850 points
Other Parts Discussed in Thread: NOWECC

Hi,

I have defined a path variable for a folder in the Linked Resources.  I am using it in a post build step and passing it to a batch file.

 

I pass it as "${NOWECC}", but the path that gets passed is blank.  I echo'd the argument and it shows as "".  Other arguments that I pass using the PROJECT_ROOT variable get passed OK.

 

Post build step:

"${PROJECT_ROOT}/Utilities/BuildFiles/SRBPostBuildSteps.bat" "${PROJECT_ROOT}" "${NOWECC}" "${PROJECT_ROOT}\Debug"

Output:

var 1

"C:/Users/sabolda/Desktop/TFS/FW UX/SRB"

var 2

""

var 3

"C:/Users/sabolda/Desktop/TFS/FW UX/SRB\Debug"

  • 0
    TI__Guru**** 451281 points

    Hi David,

    Can you try explicitly setting NOWECC as a Build Variable also and see if that works?

    Thanks

    ki

  • 0 in reply to Ki
    Genius 4850 points

    That seems to work OK.  Is that the proper way to specify the variable?

  • 0 in reply to David Sabol
    TI__Guru**** 451281 points

    Build Variables and Linker Resource Path Variables are separate things.

    Linked Resource Path Variables are only to be used when linking source files.

    Build Variables are to be used in your build properties (compiler options, post buid steps, etc). \

    Technically they are not supposed to overlap. For example, you aren't supposed to be able to use Linked Resource Path Variables in your build properties just like Build Variables can't be used to link source files.

    However, this separation caused confusion among people who didn't know the clear differences (to them it is just an environment variable of some sort that can be used everywhere). So we eventually set it up so that creating a Linked Resource Path Variable also applied it to the Build Variables. I can't remember when this happened - in CCSv6 for sure and some of the later v5 versions I think (maybe 5.5).

    In 6.0.1 we will make it even clearer