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 creates linked resource which overrides Linker file search path?

We have a project with CCS 6.1 structured like this:

  • Main CCS project with microcontroller target
    • Imported Tivaware library (usblib)
    • Imported Tivaware library (driverlib)
    • Imported custom library which we wrote (otherlib)

Each of these four projects are imported into the workspace, and we set up search paths (Project Properties -> Build -> ARM Linker -> File search path) to usblib, driverlib, and otherlib. However, CCS seems to create a linked resource listed in Resources -> Linked Resources at some later time for driverlib and otherlib. These linked resources are either to an absolute or relative file path, and seem to take precedence over the file search paths we set up.

The result is that our build configurations have no effect for the libraries which have these linked resources automatically created. The workaround is to continue to go into Resources -> Linked Resources and delete them, and then the builds work as expected.

Is this a known issue? What is causing CCS to automatically create these linked resources?

  • Host: Win7 64-bit, SP1, in VM
  • CCS version: 6.1.0.00104
  • Hardware n/a (occurs during compilation)

  • Eric Pruett said:
    However, CCS seems to create a linked resource listed in Resources -> Linked Resources at some later time for driverlib and otherlib.

    That is odd. Are you saying that these linked resources are not there when the project is created/imported into the workspace but something is adding them later? 

    Have you been able to identify exactly when they are getting added? Is it during the build process? 

    If you can provide a simple project (and steps to follow) to reproduce the issue, that could be very helpful for us to investigate this further.

  • Thanks Aarti.

    I cannot identify exactly when the linked resource is created. I will keep an eye on it and try to notice the next time they are created and report back.
  • Just to follow up, we have not been able to reproduce this issue, so it must have been an incorrect configuration from one of our developers at some time.