• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 491 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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/CCSTUDIO: Add Lib Directories to Indexer for Makefile Projects

Christian Harris
Prodigy 20 points
Part Number: CCSTUDIO
Other Parts Discussed in Thread: AM3358

Tool/software: Code Composer Studio

In "1.7 Linux Board Porting Series - Module 7 - Debugging U-boot with JTAG in CCS", Steve explains that CCS marks undefined symbols as bugs due to the fact that the indexer does not parse the makefile(s). He comments that while CCS shows the bug marks, it will not impact the build of the project as the build is managed by the specified [cross]compiler in said makefiles. He noted it is possible to configure CSS to parse the extra libraries, though time consuming.

I am hoping that someone can give directions on how to configure CCS (or the indexer) to search additional library paths and remove the bug marks. I am interested in this for both the debugging aspect, and probably more so for the "Open Declaration" function. I am working on a beaglebone black (like in the video) to deep dive and study the am3358 along with u-boot. It would be very useful if the symbols all resolved correctly. Steve says it can be done, but gives not hint how to go about it.

  • 0
    TI__Guru**** 464431 points

    Hi Christian,

    Christian Harris said:
    Steve explains that CCS marks undefined symbols as bugs due to the fact that the indexer does not parse the makefile(s). He comments that while CCS shows the bug marks, it will not impact the build of the project as the build is managed by the specified [cross]compiler in said makefiles.

    I assume these "errors" are from Codan - CDT's static code analysis tool. And yes, they can be safely ignored as it will not impact the build.

    Christian Harris said:
    I am hoping that someone can give directions on how to configure CCS (or the indexer) to search additional library paths and remove the bug marks

    It is documented in the CDT help:

    https://help.eclipse.org/neon/index.jsp?topic=%2Forg.eclipse.cdt.doc.user%2Ftasks%2Fcdt_t_proj_paths.htm

    Note that when I tried this, I had to use the option to set it up in MBS via "Paths and Symbols" project properties (mentioned in the article above). It looks like in CCS, the option to modify the entries for the Language Settings Providers was greyed out. I need to check to see if that is by design or not.

    Thanks

    ki