• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 54 subscribers
  • Views 3235 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 target configuration relative paths

Alastair Hoyle
Prodigy 70 points

Hi

I like to have my .launch and .ccxml target configuration files in the main project directory. However, my projects don't live in fixed directories., My colleagues and I work on various versions of the code each in this own directory. What I would like to do is set up the debugging enviroment with relative paths to the target configuration and programs. So that we have a constant .launch file that correctly reference the target configuration file and program file in the same or sub-directories.

I have tried using normal relative paths "./Debug/xxx.out" and "./MyConfig.ccxml" but it complains that they don't exist.

I have tried using workspace relative name ${workspace_loc:/${ProjName}/Debug/xxx.out}

I have tried using ${PROJECT_LOC}/MyConfig.ccxml

The debugger works fine when I give it absolute path, but obivous that can be confusing when I forget to update one of the path and I find I am debugging a different version of the code that what I expected.

How can I use relative paths to set up the debugger?

Kindest regards

  • 0
    TI__Guru**** 466071 points

    Hello,

    For your out file, you can use: ${build_artifact:nameofmyproject}

    This will pick up the out file in the configuration subdirectory of the active configuration of the project

    For your ccxml: ${target_config_active_default:nameofmyproject}

    This will pick up the active target configuration file of the active configuration.

    Pure relative paths like (./folder/file.out) is not supported inside the launch config. Same with project level variables like $(ProjName)

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 70 points
    Hi Ki

    Thanks for that.

    Is there anyway to change the target parameters depending on the build configuration? I have two build configurations, one to run out of RAM and the other from FLASH. I have to manually check the target "Flash Program Settings" are correctly set in the debug configuration. I could define two debugging configuraturations, but I would what to be sure the correct debug configuration was selected by the developer depending on the currently selected build configuration. Can this be done?

    Many Thanks
    Alastair
  • 0
    Expert 1220 points
    You can look at this post as well for an image-based explanation:

    e2e.ti.com/.../1741346