• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 480 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

PATH variable name changing when copying linked files from one project to another project

stevenh
Guru 20035 points
Other Parts Discussed in Thread: CONTROLSUITE

Hello,

I noticed that when I copy a linked file from one project to another, CCS creates a new PATH variable and makes the copied linked file relative to that path variable.

For example, if the linked file was relative to ABC path variable, a new path variable ABC1 is created and the linked file will be made relative to ABC1.

The project I am copying the linked file to already has a path variable with the same name (ABC), so why would it create a new path variable and not use the existing path variable?

Is there any way to stop CCS from creating the new path variable?

Stephen

  • 0
    TI__Genius 15190 points

    Hello Stephen, 

    Could it be that the two paths resolve to different directories? Could you open project properties and then expand Resource->Linked Resources category and look at "Path Variable" tab. It should show all linker resource paths, you should be able to see actual resolved paths there. If they point to the same physical direcotry, (ABC and ABC1), then is there any way that you could provide a bit more detail in how linked resource paths were created? A sample projects would be ideal, but I am not sure if it is possible. 

    I tried importing couple of projects from ControlSuite SW package, which use linked resources quite heavily and copying couple of linked files from one project to another did not create duplicate linked resource path variables. 

    martin

  • 0 in reply to MartinS
    Guru 20035 points

    Hello Martin,

    It seems to be happening with one specific project, so its not that big of issue right now.  I just tried it out right now and noticed it's using the other path variable (i.e. ${ABC}) as the path for the new path name. I previously thought it was using the full path name.

    Stephen