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.

Eclipse macros don't work in CCSv5 Debug Configurations



${WorkspaceDirPath} doesn't work in CCSv5 Debug Configurations for CCXML file. I would expect that 'Workspace' button will use this macro to make Debug configuration portable with workspace. However, CCSv5 uses absolute path. Attempt to manually add this macro fails - ccxml file is not recognized.

How do I make Debug launch configuration portable?

Thanks,

Eugene

  • Hi Eugene,

    what portability do you need? 

    I have tried the following and verified that the ccxml file is included.

    1) Created a project and attached a ccxml to it selecting "copy" instead of link

    2) File->Export->General->Archive and made sure to have everything selected for export to the archive file

    3) when importing, the ccxml file witl be there

    Is this something you were looking for or would be useful for you?  Please keep us informed.

    Best Regards,
    Lisa

  • Lisa,

    Importing is not an option. I am trying to establish baseline workspace with global preferences and launches which are tuned to the user desires. New project source is imported into this baseline workspace through CCS command line. The whole procedure is automated with minimal user involvement.

    It all works fine with exception of CCXML file which has absolute path in CCS launch.

    I believe that it is common in Eclipse environment to have launches which use workspace macros.

    On the other hand, do you have command line option which will allow me to import CCXML and pre-configured launches?

    Regards,

    Eugene

  • Eugene,

    There is no support for variable expansion for the ccxml file path in the launch dialog. I have filed a CQ to track this issue, SDSCM00043033.

    Regards,
    Patrick

  • Eugene,

    You can use this macro for the ccxml file in the launch configuration, "target_config_active_default:<project_name>". Replace <project_name> with the name of the project and put the .ccxml file within the project.

    Regards,
    Patrick

  • patch said:

    Eugene,

    You can use this macro for the ccxml file in the launch configuration, "target_config_active_default:<project_name>". Replace <project_name> with the name of the project and put the .ccxml file within the project.

    Regards,
    Patrick

    It does not work in my case (or I have not understood how to write the macro).

    Has someone tried it?

    KR,

    Gianluca