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

Relative paths in the debug configurations

Pial
Expert 7280 points

Hello everyone,

Does anyone know if it is possible to use relative paths instead of absolute paths when using the debug configuration to load a specific .out program ?

I tried using global variables but it seems to be unrecognised by this part of the program..

One workaround would be to be able to specify a specific build configuration while selecting the project to be loaded, but again, I could not find any way to do so..

I add some screenshots bellow to illustrate the problem:

The absolute path problem:

The miss of configuration selection while adding the file by selecting the project :

Many thanks in advance for your support,

Pierre-Alexandre Deltrieux

Digital FAE

  • 0
    TI__Guru*** 130875 points

    Hi Pierre-Alexandre,

    let me look into this for you.  What CCS version are you using?  Do you want to control where the .out file is using a variable or are you strictly talking about loading from the debug tools?

    Where have you defined the variable you are trying to use?

    Best Regards,
    Lisa

  • 0 in reply to Lisa TI
    TI__Expert 7280 points

    Lisa,

    I am currently using CCS v5.1.

    I am talking about loading the .out from the Debug file.

    In fact, my project includes several configurations, compiling with different options.

    I created several debug configurations, loading each time a different .out file, from each builded configuration.

    The problem is that when locating the .out in the debug configuration editor, I cannot use a relative path, only absolute path.

    The variable used was for example ${PROJECT_LOC}, or WORKSPACE_LOC, as bellow :

    ${WORKSPACE_LOC}\testProject\Conf 1\testProject.out

    I cannot understand why it wouldn't work..

    Thank you again !

    Best regards,

    Pierre-Alexandre Deltrieux

  • 0 in reply to Pial
    TI__Guru*** 130875 points

    Hi Pierre-Alexandre,

    try lower case ... workspace_loc since this is how it is defined in eclipse.

    In the mean time I am going to test a couple things here and get you feedback as soon as I am able.

    Best Regards,
    Lisa

  • 0 in reply to Lisa TI
    TI__Expert 7280 points

    Lisa,

    Thank you very much for your answer... using lower case solved the problem !

    I never thought of trying this..

    Thank you again,

    Best regards,

    Pierre-Alexandre

  • 0 in reply to Pial
    TI__Guru*** 130875 points

    Hi Pierre-Alexandre,

    no problem at all.  I just verified here that it is case sensistive.

    All the best.

    Best Regards,

    Lisa