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.

CCSv4.2: macros are not used when linking files to the project

Hi,

I am trying to link new files to the existing CCSv4.2 project. I have the macros.ini file in the project directory. When I try to link a new source file to the project, the environment uses the absolute path (without letting end user know). The ideal way would be that the environment can first search the macros.ini and see if it applies, or let the user choose the absolute path or a macro.

Without doing this, it is very hard to build a portable project, especially under Clearcase. It is very dangerous that some files could be from a different view than the user thought.

Currently we manually change the .project file every time we need to hand off. However we hope this feature can be added. Thanks.

Best Regards,
Gary

  • Gary Xu said:
    I am trying to link new files to the existing CCSv4.2 project. I have the macros.ini file in the project directory. When I try to link a new source file to the project, the environment uses the absolute path (without letting end user know).

    Hi Gary,

    This is expected behavior. The macros.ini is only used when importing existing CCSv4 projects into another workspace. On import, CCS will add any variables in the macros.ini file to the Linked Resources variables list. The macros.ini file is not used again after that (by the workspace).

    The way to add a linked file using a macro from CCS (without modifying the .project file) is described here (see slide 19 of):

    http://processors.wiki.ti.com/images/0/09/CCSv4_Tips_%26_Tricks.pdf

    Thanks

    ki

     

     

  • Hi Ki-Soo,

    Thank you for the reply. I tried the method you mentioned and it works.

    However, I wish similar capabilities can extend to "Link Files to Project" window. It is more intuitive than the "New->file" path. Thanks.

    Best Regards,
    Gary