• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 54 subscribers
  • Views 1179 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.

Creating variables in CCS

Johnny Kim1
Expert 7295 points

I have a question about creating Variables in CCS.

 

Case 1.

XDC_CG_ROOT     ${ROOT_DIR}\xdctools_3_24_03_33

  -> Okay

Case 2.

TEMP1     xdctools_3_24_03_33

XDC_CG_ROOT     ${ROOT_DIR}\${TEMP1}  -> Not okay( To create XDC_CG_ROOT variable, TEMP1 variable is used.)

 

Case 1 and case 2 seem that back-slash behaves differently even though same compiler is used.

Is there anyone who can explain above?

  • 0
    TI__Guru**** 173310 points

    Can you check if it works if you use forward slashes instead of backward slashes for the paths when creating all your variables?
    I just tried a small test and it worked fine.

    So set the variables as follows:

    TEMP1          xdctools_3_24_03_33
    XDC_CG_ROOT     ${ROOT_DIR}/${TEMP1} 

  • 0 in reply to AartiG
    TI__Expert 7295 points

    Thank you for your comment.

    Yes, you are right.

    But the point is this.

    Case 1.
    XDC_CG_ROOT                 ${ROOT_DIR}\xdctools_3_24_03_33
     
    Case 2.
    TEMP1                                  xdctools_3_24_03_33
    XDC_CG_ROOT                    ${ROOT_DIR}\${TEMP1}

    -> case 1 and case2 use "same backward slash" but its behavior is different.
         So my customer wants to know why this happens?

    Thank you.

  • 0 in reply to Johnny Kim1
    TI__Guru**** 173310 points

    I am checking into this and will post an update when I have more information.

  • 0 in reply to AartiG
    TI__Expert 7295 points

    Thank you very much for your interest in this.

    Regards,

    Johnny

  • 0 in reply to Johnny Kim1
    TI__Genius 9435 points

    Johnny, 

    I don't really have an answer to why a single backslash gets lost in that case...Double backslash works in that same scenario.  But, just like Aarti, I would recommend using forward slashes always.

    Backslashes can cause problems, as both Gmake and the Windows command-line interpreter sometimes treat the backslash as an escape character.  For example, if your command includes a double-quoted path which ends in a backslash (e.g. --include_path="c:\temp\"), the Windows interpreter would treat the backslash as the escape character for the double-quote.

    Thanks,

    - Baltasar