• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 52 subscribers
  • Views 1679 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.

Source lookup path in CCSv4 (4.1.3.00038)

Eugene K
Expert 1685 points

Is there a way to automatically redirect CCS to search for a source file from the library in different folder if embedded into DWARF information points to non existing on a given PC location?

I tried Project->Properties->CCS Debug->Source Lookup Path  and added new folder tree with search sub folders checked but it did not work.

If I manually point to new folder for each missing file then CCS finds it. Is there any other setting to make source look up work?

Thansk,

Eugene

  • 0
    TI__Guru**** 450031 points

    Starting at slide 41 of: http://processors.wiki.ti.com/images/0/09/CCSv4_Tips_%26_Tricks.pdf are all the main options for setting source lookup paths.

    Eugene K said:
    Is there a way to automatically redirect CCS to search for a source file from the library in different folder if embedded into DWARF information points to non existing on a given PC location?

     I'm not quite sure what the scenario here is. Did the source file locations change since the library was built?

  • 0 in reply to Ki
    Expert 1685 points

    Ki,

    Sorry for not making it clear. Yes, source location for library file has changed. Lets say that libraries were built on one workstation and the project debugged on another.

    What you are referring to on slide 41 is what works. The method described on slide 43 does not seem to work. Maybe slide 42 will work. I'll give it a try.

    Thanks,

    Eugene

  • 0 in reply to Eugene K
    Expert 1685 points

    Ki,

    No, only slide 41 method works. The problem with slide 41 method is that users may not know which one of tens of library source folders contain the missing file.

    Thanks,

    Eugene